From: Daniel Jacobowitz <drow@mvista.com>
To: Johan Walles <johan.walles@appeal.se>
Cc: gdb@sources.redhat.com
Subject: Re: Trouble debugging a Java Virtual Machine on Linux
Date: Thu, 24 Jan 2002 09:21:00 -0000 [thread overview]
Message-ID: <20020124122126.B26301@nevyn.them.org> (raw)
In-Reply-To: <3C500AAC.5030709@appeal.se>
On Thu, Jan 24, 2002 at 02:22:52PM +0100, Johan Walles wrote:
> Now, I'd like very much to get some input from somebody knowledgable
> about gdb. First, is there already some simple way of interfacing with
> gdb to tell it to use our functions for managing processes and not its
> own? If not, does patching gdb seem like a reasonable solution? What
> would have to happen for these patches to get accepted into the official
> gdb?
Oh, the other thing I meant to mention. For your last question:
- the patches would need to be clean and not overly target-specific
- the copyright on them would need to be assigned to the FSF. I don't
remember the address to ask for paperwork - fsf-records@gnu.org?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-01-24 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 5:23 Johan Walles
2002-01-24 9:19 ` Daniel Jacobowitz
2002-01-24 23:23 ` Johan Walles
2002-01-24 9:21 ` Daniel Jacobowitz [this message]
2002-01-24 9:29 ` Andrew Cagney
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=20020124122126.B26301@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=johan.walles@appeal.se \
/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