From: Michael Snyder <msnyder@specifix.com>
To: John Carter <john.carter@tait.co.nz>
Cc: gdb@sourceware.org
Subject: Re: What does gdb stub need for thread aware debugging on embedded system?
Date: Mon, 16 Jun 2008 00:20:00 -0000 [thread overview]
Message-ID: <1213575599.3601.898.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.00.0806161145460.17082@parore.tait.co.nz>
On Mon, 2008-06-16 at 12:09 +1200, John Carter wrote:
> I'm looking to get thread aware debugging running on our "sparc-alike"
> Leon II processor.
>
> Unlike the usual sparc stub, I cannot get thread information from
> Solaris as we're not running solaris on this device.
>
> If I understand things correctly, getting gdb working should just be a
> matter of tying gdb/sparc-stub.c to our serial ports by defining
> extern void putDebugChar(); /* write a single character */
> extern int getDebugChar(); /* read and return a single char */
>
> Grepping through that code the word "thread" doesn't occur.
>
> What I'm missing is how does gdb get information about threads from
> the devices OS to gdb running on the desktop.
>
> Any pointers to the right bit of documentation / code would be most
> welcome.
At the time that that code was written, threads were very far from
the minds of people who wrote remote gdb stubs!
Look at gdbserver -- it has support for threads.
next prev parent reply other threads:[~2008-06-16 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 0:10 John Carter
2008-06-16 0:20 ` Michael Snyder [this message]
2008-06-16 1:44 ` Daniel Jacobowitz
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=1213575599.3601.898.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb@sourceware.org \
--cc=john.carter@tait.co.nz \
/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