This is the mail archive of the gdb-testers@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[binutils-gdb/gdb-8.0-branch] Python: Use correct ptid in btrace recording


*** TEST RESULTS FOR COMMIT ee53a929a4c74456661f60741ec22139e06ebc70 ***

Author: Tim Wiederhake <tim.wiederhake@intel.com>
Branch: gdb-8.0-branch
Commit: ee53a929a4c74456661f60741ec22139e06ebc70

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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]