projects / deliverable / binutils-gdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8d0050e) | patch
Python: Use correct ptid in btrace recording
authorTim Wiederhake <tim.wiederhake@intel.com>
Tue, 2 May 2017 09:35:54 +0000 (11:35 +0200)
committerTim Wiederhake <tim.wiederhake@intel.com>
Tue, 2 May 2017 09:35:54 +0000 (11:35 +0200)
commitae20e79ae852fee8f7d42701a54a95de3b79ecea
tree616d593dcb7ef8249449028538998a7ff6a180e4tree | snapshot
parent8d0050ea192c41349c1f2b000866c1bdb761abebcommit | diff
Python: Use correct ptid in btrace recording

The user would always get the instruction_history and function_call_history
objects of the current thread, not the thread for which the gdb.Record object
was created.

The attached testcase fails without this patch and passes with the patch.
gdb/ChangeLog diff | blob | blame | history
gdb/btrace.c diff | blob | blame | history
gdb/python/py-record-btrace.c diff | blob | blame | history
gdb/python/py-record.c diff | blob | blame | history
gdb/python/py-record.h [new file with mode: 0644] blob
gdb/testsuite/ChangeLog diff | blob | blame | history
gdb/testsuite/gdb.python/py-record-btrace-threads.c [new file with mode: 0644] blob
gdb/testsuite/gdb.python/py-record-btrace-threads.exp [new file with mode: 0644] blob
GDB Binutils - Deliverables
This page took 0.029872 seconds and 4 git commands to generate.