This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb-gdbserver, non-stop, async - thread identifier more than only a thread id?
- From: Tom Tromey <tromey at redhat dot com>
- To: "D. Lehne" <daniel dot lehne at amk-drives dot bg>
- Cc: gdb at sourceware dot org
- Date: Wed, 06 Jul 2011 14:57:49 -0600
- Subject: Re: gdb-gdbserver, non-stop, async - thread identifier more than only a thread id?
- References: <4E0F230A.70601@amk-drives.bg>
>>>>> "D" == D Lehne <daniel.lehne@amk-drives.bg> writes:
D> There are 3 threads, but it isn't clear which thread represents which
D> functionality (fucntion call) . When a thread is created, isn't it
D> possible to refer the first function call on stack as an reference
D> name of a thread?
I guess it would be possible, but I don't know if it is desirable.
You can name threads manually now. So, you could perhaps script this if
you wanted.
Tom