From: Andreas Schwab <schwab@suse.de>
To: Vladimir Vorobyov <vladimir.vorobyov@iss.org.ua>
Cc: gdb@sources.redhat.com
Subject: Re: pthreads debug with gdbserver
Date: Sat, 20 Nov 2004 17:13:00 -0000 [thread overview]
Message-ID: <jesm74sbla.fsf@sykes.suse.de> (raw)
In-Reply-To: <20041120164209.GA15174@nevyn.them.org> (Daniel Jacobowitz's message of "Sat, 20 Nov 2004 11:42:10 -0500")
Daniel Jacobowitz <drow@false.org> writes:
> Take a look at the source code to gdbserver. Andreas, now I remember
> why I enabled thread_db support on a per-target basis - there are other
> support routines that have to be written.
Yes, I have noticed that, too. I'm currently trying to get it working for
m68k (plus support for PTRACE_GETREGS).
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-11-20 16:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 14:23 Vladimir Vorobyov
2004-11-19 14:42 ` Daniel Jacobowitz
2004-11-19 15:59 ` Vladimir Vorobyov
2004-11-20 10:01 ` Daniel Jacobowitz
2004-11-20 16:42 ` Vladimir Vorobyov
2004-11-20 16:57 ` Daniel Jacobowitz
2004-11-20 17:13 ` Andreas Schwab [this message]
2004-11-20 17:38 ` Vladimir Vorobyov
2004-12-06 18:41 ` NPTL on ppc (was: pthreads debug with gdbserver) Linh Dang
2004-12-06 18:45 ` Daniel Jacobowitz
2004-12-06 19:56 ` NPTL on ppc Linh Dang
2004-12-06 20:18 ` Daniel Jacobowitz
2004-12-06 22:41 ` Andreas Schwab
2004-12-06 23:20 ` Andreas Schwab
2004-12-07 14:33 ` Linh Dang
2004-12-07 14:56 ` Andreas Schwab
2004-12-06 22:04 ` Andreas Schwab
2004-11-22 14:07 ` pthreads debug with gdbserver Vladimir Vorobyov
2004-11-22 18:04 ` Daniel Jacobowitz
2004-11-23 19:33 ` Vladimir Vorobyov
2004-11-19 16:19 ` Andreas Schwab
2004-11-19 17:30 ` Vladimir Vorobyov
2004-11-20 1:31 ` Andreas Schwab
2004-11-20 1:32 ` 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=jesm74sbla.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@sources.redhat.com \
--cc=vladimir.vorobyov@iss.org.ua \
/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