From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Triggering qSymbol packets
Date: Thu, 19 Jan 2006 03:26:00 -0000 [thread overview]
Message-ID: <20060119020306.GB23692@nevyn.them.org> (raw)
In-Reply-To: <43CEE12E.90504@itee.uq.edu.au>
On Thu, Jan 19, 2006 at 10:45:34AM +1000, John Williams wrote:
> I got it from here:
>
> http://www.cygwin.com/ml/gdb/2002-02/msg00098.html
>
> I looked but didn't find any current references that describe gdbserver
> + pthread debugging - if there's something obvious I'm missing please
> let me know.
Well, that's a shame. The implementation eventually merged wasn't that
one, and his advice is not useful today.
There's inadequate documentation for this process and it could use a
good FAQ; it comes up on this list about twice a month.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-19 2:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 0:19 John Williams
2006-01-19 0:46 ` Daniel Jacobowitz
2006-01-19 0:50 ` John Williams
2006-01-19 1:18 ` Jim Blandy
2006-01-19 3:26 ` Daniel Jacobowitz [this message]
2006-01-20 4:42 ` John Williams
2006-01-20 20:29 ` Jie Zhang
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=20060119020306.GB23692@nevyn.them.org \
--to=drow@false.org \
--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