Ignore this. It was caused by a home-grown thread abstraction
always referring to the 'main' thread. It looks like this is the
cause of the other faults I've been having as well.
Cheers
From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Simpson, John
Sent: 13 November 2007 09:52
To: fedora-list@xxxxxxxxxx
Cc: Pyle, Andy
Subject: How do I get the same thread id as supplied by 'ps -AL' in LWPcolumn
| *** WARNING *** This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. |
Hi
I'm running
2.6.18-1.2786.fc6 and I'm trying to debug an extravagantly threaded program
(sixteen separate threads, not my code).
The problem I've got
is that although each of the threads is uniquely identifiable using 'ps -AL' or
'/proc/PID/task' (information which is also available on creation and
destruction to gdb) I cannot get the same identifiers programmatically.
I've tried pthread_self() and syscall(_NR_gettid) but they just return the
identifier of the initiating thread rather than the thread I'm calling them
from. This makes debugging extremely difficult, for example I can see from
'ps -AL' that some of the threads are doing the <defunct> zombie thing,
but I don't know which ones they are.
Any
suggestions
Thanks
John
| ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. MBDA UK Limited, a company registered in England and Wales, registration number 3144919 whose registered office is at Six Hills Way, Stevenage, Hertfordshire, SG1 2DA, England. ******************************************************************** |
