From: "Veenu Verma (AS/EAB)" <veenu.verma@ericsson.com>
To: <gdb@sourceware.org>
Subject: Thread exit & create events
Date: Fri, 24 Aug 2007 08:51:00 -0000 [thread overview]
Message-ID: <9171BA436A79BF46953672FB5A11DA5E012B45C6@esealmw104.eemea.ericsson.se> (raw)
Hello
We are integrating GDB back end with DSF ( Debugger Services Framework )
in Eclipse.
Found two stumbling blocks around thread exit/create events
1. Though GDB raises a thread exit event but -thread-list-ids command
still list the reported exited thread for quite some time.
There is a gap till I guess the thread completely exits. Only info
threads give the hint by using "Exiting" in information.
This is a problem for us as we are relying on events and thread-list-ids
commands to paint the GUI.
Info threads is used sparingly from front end.
Can -thread-list-ids command take into account the exited threads ? Is
it difficult to achieve this in GDB ?
2. GDB thread identifier is not speicified when a thread is created or
exited. Only system identifier is used.
Again thread-list-ids uses only gdb thread identifier. Hence, the
mismatch and the problem.
Since on HP-UX systems gdb thread identifier is shown, I'm guessing it
shouldn't be hard to do the same for Linux.
Is there a reason for not to have gdb identifier on linux or it's just
that it's not done yet.
Veenu Khanna Verma
Ericsson - PDU Packet Server Platform
Veenu Khanna Verma
+46 7 38 09 33 09 / +46 8 727 36 05
AS/EAB/FTI/GT TADE Design
Ericsson - PDU Packet Server Platform
next reply other threads:[~2007-08-24 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 8:51 Veenu Verma (AS/EAB) [this message]
2007-08-24 10:46 ` Mark Kettenis
2007-08-24 12:00 ` Daniel Jacobowitz
2007-08-24 12:14 ` Veenu Verma (AS/EAB)
2007-08-24 12:19 ` Daniel Jacobowitz
2007-08-24 13:15 ` Veenu Verma (AS/EAB)
2007-08-24 13:20 ` Daniel Jacobowitz
2007-08-24 18:25 ` Jim Blandy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9171BA436A79BF46953672FB5A11DA5E012B45C6@esealmw104.eemea.ericsson.se \
--to=veenu.verma@ericsson.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox