-
- Downloads
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.
Showing
- gdb/ChangeLog 12 additions, 0 deletionsgdb/ChangeLog
- gdb/btrace.c 7 additions, 1 deletiongdb/btrace.c
- gdb/python/py-record-btrace.c 20 additions, 12 deletionsgdb/python/py-record-btrace.c
- gdb/python/py-record.c 1 addition, 16 deletionsgdb/python/py-record.c
- gdb/python/py-record.h 40 additions, 0 deletionsgdb/python/py-record.h
- gdb/testsuite/ChangeLog 5 additions, 0 deletionsgdb/testsuite/ChangeLog
- gdb/testsuite/gdb.python/py-record-btrace-threads.c 58 additions, 0 deletionsgdb/testsuite/gdb.python/py-record-btrace-threads.c
- gdb/testsuite/gdb.python/py-record-btrace-threads.exp 81 additions, 0 deletionsgdb/testsuite/gdb.python/py-record-btrace-threads.exp
Loading
Please register or sign in to comment