From: Andrew Cagney <ac131313@cygnus.com>
To: Quality Quorum <qqi@theworld.com>, Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Snyder <msnyder@redhat.com>,
"Sarnath K - CTD, Chennai." <k_sarnath@ctd.hcltech.com>,
gdb@sources.redhat.com
Subject: Re: Thread Support for remote debugging
Date: Thu, 31 Jan 2002 19:29:00 -0000 [thread overview]
Message-ID: <3C5A0B8B.7080504@cygnus.com> (raw)
In-Reply-To: <Pine.SGI.4.40.0201311815360.10971237-100000@shell01.TheWorld.com>
>> No, he means "knowing whether GDB and GDB Server support doing remote
>> debugging at all", as far as I can tell.
>>
>> We've covered this ground a couple times lately :) Someone promised to
>> contribute thread support and dropped off the face of the earth. It's
>> on my TODO list, but I don't anticipate getting to it any time soon.
>> Etc.
(I recall the discussion, from memory one of the problems was the paper
trail). Daniel, you might consider doing what I do with my TODO list -
just shove it all into GDB's bug database as change-requests :-)
> If you are talking about me, I had it done more than one year ago:
> http://world.std.com/~qqi, see section about gdb.
Daniel isn't.
> The problem is that (1) redhat never said 'yes we want it' so it is
> sitll based on 4.18, (2) there are a few issues which could be
> resolved one way or anotehr an readhat never said 'we want it this way'.
(GDB is owned by the FSF (not Red Hat) and it is assumed that GDB
developers put the FSF's interests before their own.)
GDB currently comes with:
gdb/*-stub.c:
These are primative stubs that can be run on embedded boards.
They appear to be public domain.
gdb/gdbserver:
This lets you debug a native UNIX program on a remote machine.
It is GPLed. It is owned by the FSF.
Within the embedded community I suspect it is a hot product
since it lets the developer debug a UNIX application
running on the embedded machine remotely.
My understanding of rproxy was that it could be linked with third party
libraries and provide a remote protocol interface to JTAG devices and
the like. I wasn't aware that it could be used to do remote debugging
of native applications.
As for making rproxy part of GDB, I'm certainly interested (I didn't
know you were looking to do this). Since gdbserver is both owned by the
FSF and is GPL, I would need to ensure that its replacement is no less
``free''. Would you be willing to contribute rproxy to the FSF?
Andrew
next prev parent reply other threads:[~2002-02-01 3:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 1:11 Sarnath K - CTD, Chennai.
2002-01-21 6:07 ` Daniel Jacobowitz
2002-01-21 7:10 ` Quality Quorum
2002-01-21 8:38 ` Andrew Cagney
2002-01-31 12:47 ` Michael Snyder
2002-01-31 15:12 ` Daniel Jacobowitz
2002-01-31 15:22 ` Quality Quorum
2002-01-31 17:22 ` Daniel Jacobowitz
2002-01-31 19:41 ` Quality Quorum
2002-01-31 19:29 ` Andrew Cagney [this message]
2002-01-31 19:44 ` Quality Quorum
2002-01-31 15:41 ` Michael Snyder
2002-01-31 17:18 ` Daniel Jacobowitz
2002-01-31 17:21 ` Michael Snyder
2002-01-21 22:08 Sarnath K - CTD, Chennai.
2002-01-31 23:32 Korbel, Michal
2002-02-01 7:45 ` Dan Kegel
2002-02-01 8:13 Korbel, Michal
2002-02-01 8:27 ` Dan Kegel
2002-02-01 9:43 ` Quality Quorum
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=3C5A0B8B.7080504@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=k_sarnath@ctd.hcltech.com \
--cc=msnyder@redhat.com \
--cc=qqi@theworld.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