From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@specifix.com>
Cc: John Carter <john.carter@tait.co.nz>, gdb@sourceware.org
Subject: Re: What does gdb stub need for thread aware debugging on embedded system?
Date: Mon, 16 Jun 2008 01:44:00 -0000 [thread overview]
Message-ID: <20080616014401.GA10193@caradoc.them.org> (raw)
In-Reply-To: <1213575599.3601.898.camel@localhost.localdomain>
On Sun, Jun 15, 2008 at 05:19:59PM -0700, Michael Snyder wrote:
> At the time that that code was written, threads were very far from
> the minds of people who wrote remote gdb stubs!
Yeah. While sparc-stub.c is a valid example, keep in mind that it is
a very old one. There's been a tremendous amount of change in the
remote protocol since then, including in the threads area (see
e.g. the description of vCont in the remote protocol documentation,
which is in the GDB manual).
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-06-16 1:44 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
2008-06-16 1:44 ` Daniel Jacobowitz [this message]
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=20080616014401.GA10193@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=john.carter@tait.co.nz \
--cc=msnyder@specifix.com \
/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