aboutsummaryrefslogtreecommitdiff
path: root/ld
diff options
context:
space:
mode:
authorKevin Buettner <kevinb@redhat.com>2016-05-05 12:39:36 -0700
committerKevin Buettner <kevinb@redhat.com>2017-09-21 11:49:48 -0700
commit757bf54bb48a8417154cfdd7128c1775d43478d8 (patch)
treef6513023423e4d9c6df9c4bfa08dc2b959f25e6e /ld
parentf2ff95c5837bd41848e7156aa2677498518d0d18 (diff)
downloadgdb-757bf54bb48a8417154cfdd7128c1775d43478d8.zip
gdb-757bf54bb48a8417154cfdd7128c1775d43478d8.tar.gz
gdb-757bf54bb48a8417154cfdd7128c1775d43478d8.tar.bz2
Test case for Inferior.thread_from_thread_handle
As the title says, this is a test case for Inferior.thread_from_thread_handle, a python method which will, given a thread library dependent thread handle, find the GDB thread which corresponds to that thread handle (in the inferior under consideration). The C file for this test case causes the thread handles for the main thread and two child threads to be placed into an array. The test case runs to one of the functions (do_something()) at which point, it retrieves the thread handles from the array and attempts to find the corresponding thread in GDB's internal thread list. I use barriers to make sure that both threads have actually started; execution will stop when one of the threads breaks at do_something. Thanks to Simon Marchi for suggestions for forcing the thread numbering to be stable. gdb/testsuite/ChangeLog: * gdb.python/py-thrhandle.c, gdb.python/py-thrhandle.exp: New files.
Diffstat (limited to 'ld')
0 files changed, 0 insertions, 0 deletions