From: Hui Zhu <teawater@gmail.com>
To: "Praveen S. Solanki" <psolanki@ccs.neu.edu>
Cc: gdb@sourceware.org
Subject: Re: Query
Date: Wed, 05 Aug 2009 08:58:00 -0000 [thread overview]
Message-ID: <daef60380908050157y5663c9dayd87224919896b7fa@mail.gmail.com> (raw)
In-Reply-To: <21269332.189291249462529575.JavaMail.root@zimbra>
gdb/thread.c
gdb/linux-thread-db.c
On Wed, Aug 5, 2009 at 16:55, Praveen S. Solanki<psolanki@ccs.neu.edu> wrote:
> Hello Everybody. I am quite new to gdb and I am looking into the gdb source code these days. I need some direction in reading the source code. I am trying to figure out how does gdb finds new threads and upadates its thread_db. What if a new thread is created and gdb doesn't know about it? I am also interested to know higher level overview of gdb algorithm. I tried to read the gdb internal document but the sections I was interested in were not described ( though the headings were there ).
>
> Thanks and regards
> Praveen
>
next prev parent reply other threads:[~2009-08-05 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 8:55 Query Praveen S. Solanki
2009-08-05 8:58 ` Hui Zhu [this message]
[not found] <KKHDGEJONMMBAAAA@theglobe.com>
2000-04-01 0:00 ` Query Quality Quorum
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=daef60380908050157y5663c9dayd87224919896b7fa@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=psolanki@ccs.neu.edu \
/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