From: Wolfgang Denk <wd@denx.de>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Vladimir Gurevich <vag@paulidav.org>,
Kalpesh Jasapara <kjasapara@yahoo.com>,
gdb@sources.redhat.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: GDB server and threaded application
Date: Wed, 26 Mar 2003 17:13:41 +0100 [thread overview]
Message-ID: <20030326161346.18A0AC58BA@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 26 Mar 2003 08:41:42 EST." <20030326134141.GA32522@nevyn.them.org>
Daniel,
in message <20030326134141.GA32522@nevyn.them.org> you wrote:
>
> As usual, Wolfgang's answer is somewhat biased. GDB 5.3's
As usual? C'me on!
> Neither the version originally in HHL 2.0 nor gdb 5.2.1 supported it
> however. Kalpesh said he was trying gdb 5.3, which does.
It was not me who pointed to "our" version of the patch.
In my original posting which Vladimir quotet I answered a question
which was exactly about the GDB version in HHL 2.0 and gdb[server]
5.2.1.
> I would also like to offer Wolfgang a BIG KICK IN THE HEAD. I have
> looked at the relevant path on his FTP site that you referenced below;
> despite his name as the only name on the "ChangeLog entry" in the
> README and the claim of "we spend some work", it is my work. I wrote
> just about every line of that patch.
It is based on your patch, right. But your patch was against the (by
then) TOT of the GDB CVS. It was not very hard to back port to GDB
version 5.2 and even to 5.1.1. But yes, we _did_ spend some work on
this. Basic functionality of remote multi-thread debugging (namely
things as thread selection, stack backtraces, thread variables
printouts) worked okay. But if I remember right there were some
features though that were not working yet. Most notably, these were
asynchronous thread notification (that is, when gdbserver receive
signals upon creation of a new thread or death of an existing thread,
etc.), and single-stepping within a thread. Again, "we spend some
work".
> As usual proper credit would be appreciated.
Of course. Added to the README. Is this OK for you now? If not,
please send me a diff containing the text you want to see added.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The software required `Windows 95 or better', so I installed Linux.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-26 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 3:58 GDB server and threaded application Kalpesh Jasapara
2003-03-26 4:05 ` Daniel Jacobowitz
2003-03-26 5:39 ` Vladimir Gurevich
2003-03-26 13:41 ` Daniel Jacobowitz
2003-03-26 16:13 ` Wolfgang Denk [this message]
2003-03-27 0:00 ` Kalpesh Jasapara
2003-03-27 1:55 ` 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=20030326161346.18A0AC58BA@atlas.denx.de \
--to=wd@denx.de \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kjasapara@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=vag@paulidav.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;
as well as URLs for NNTP newsgroup(s).