From: Dan Kegel <dank@kegel.com>
To: "gdb@sources.redhat.com" <gdb@sources.redhat.com>,
"crossgcc@sources.redhat.com" <crossgcc@sources.redhat.com>
Subject: Remote Debugging Redux
Date: Fri, 01 Feb 2002 08:26:00 -0000 [thread overview]
Message-ID: <3C5AC2EB.2AA39E56@kegel.com> (raw)
For me, and probably for a lot of other people,
remote debugging is becoming increasingly important.
In particular, we need gdb's "gdbserver" to support
* multiple architectures
* multiple threads
* stl and other complex C++ stuff, compiled with gcc 3.x
There's a lot of action behind the scenes, and it's confusing
to the casual onlooker. So I'm starting to collect notes
on the subject at
http://www.kegel.com/linux/gdbserver.html
including e.g. a link to the gdbserver patches for powerpc
and arm that Daniel Jacobowitz just posted.
If anyone knows of related pages or information missing
from my page, please email me, additions and corrections
gladly accepted.
Thanks,
Dan
next reply other threads:[~2002-02-01 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 8:26 Dan Kegel [this message]
2002-02-01 8:52 ` Andrew Cagney
2002-02-01 9:24 ` Dan Kegel
2002-02-01 9:33 ` 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=3C5AC2EB.2AA39E56@kegel.com \
--to=dank@kegel.com \
--cc=crossgcc@sources.redhat.com \
--cc=gdb@sources.redhat.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