[asterisk-dev] Asterisk vs system thread IDs

Kirill Katsnelson kkm at adaptiveai.com
Tue Feb 15 02:11:48 CST 2011

On 110215 0000, Tilghman Lesher wrote:

> Well, there's your problem.  The numbers in the FOURTH column are identical
> to the numbers in the output of 'core show threads'.  You're just looking
> in the wrong place.  The numbers in the second column are merely indices,
> for the purpose of simplifying debugging.  They are not intended to be used
> outside of gdb:
>    6 Thread 0x7f07860e4700 (LWP 10758)  0x00007f07b4439f93 in *__GI___poll
> (fds=<value optimized out>, nfds=<value optimized out>, timeout=1000) at
> ../sysdeps/unix/sysv/linux/poll.c:87

Thank you. I missed that. Unfortunately, that's true for live process 
only. When loading a core file, however, thread's systag "Thread 
0x7f0786068700 (LWP 10759)" becomes "process 10759". So that long number 
part is lost.

You are right, that's a gdb question. I just thought maybe you have some 
best practices you might be willing to share.


More information about the asterisk-dev mailing list