summaryrefslogtreecommitdiff
path: root/gdb/bsd-uthread.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@ericsson.com>2017-02-23 10:36:20 -0500
committerSimon Marchi <simon.marchi@ericsson.com>2017-02-23 10:36:20 -0500
commit8eaf53202ea60191162d5f1069cd08ebd9f38f6c (patch)
tree24cd2ddad27fbf671e00403fc5e521e0263b5e7d /gdb/bsd-uthread.c
parent60abdbedb2b36bcae7abee2747ec027f5f2c9b91 (diff)
downloadbinutils-gdb-8eaf53202ea60191162d5f1069cd08ebd9f38f6c.tar.gz
Fix usage of inferior_ptid in two thread_alive implementations
While inspecting some target code, I noticed that in these two implementations of thread_alive, inferior_ptid is referenced directly instead of using the ptid passed as parameters. I guess that it is wrong, although I can't really test it in both cases. gdb/ChangeLog: * bsd-uthread.c (bsd_uthread_thread_alive): Use ptid instead of inferior_ptid. * go32-nat.c (go32_thread_alive): Likewise.
Diffstat (limited to 'gdb/bsd-uthread.c')
-rw-r--r--gdb/bsd-uthread.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/bsd-uthread.c b/gdb/bsd-uthread.c
index 41c7d59be19..20eecd38799 100644
--- a/gdb/bsd-uthread.c
+++ b/gdb/bsd-uthread.c
@@ -401,7 +401,7 @@ bsd_uthread_thread_alive (struct target_ops *ops, ptid_t ptid)
{
enum bfd_endian byte_order = gdbarch_byte_order (target_gdbarch ());
struct target_ops *beneath = find_target_beneath (ops);
- CORE_ADDR addr = ptid_get_tid (inferior_ptid);
+ CORE_ADDR addr = ptid_get_tid (ptid);
if (addr != 0)
{