From: Daniel Jacobowitz <drow@mvista.com>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: gdb@sources.redhat.com
Subject: Re: What has replaced fork to launch external commands?
Date: Mon, 17 Feb 2003 17:27:00 -0000 [thread overview]
Message-ID: <20030217172738.GA19524@nevyn.them.org> (raw)
In-Reply-To: <1045501672.2505.25.camel@cambridge.braddahead>
On Mon, Feb 17, 2003 at 05:07:52PM +0000, Alex Bennee wrote:
> On Mon, 2003-02-17 at 17:00, Daniel Jacobowitz wrote:
> > On Mon, Feb 17, 2003 at 04:49:25PM +0000, Alex Bennee wrote:
> > Where'd you get this 20020211 GDB? I don't remember GDB ever having a
> > "fork" command.
>
> >From ST's SH linux tools. Based on the original Monta Vista ones IIRC. I
> guess they must of patched gdb. If I can check-out the 20020211 source
> code from CVS I'll diff against the supplied sources and see what they
> changed.
>
> It would help if I knew which branch it came from.
If so I'm guessing it came from ST; MontaVista didn't add this command
either.
> > Meanwhile you can probably roughly use "shell" if I'm understanding
> > what you're doing.
>
> Mmm, tried that but it ends up echoing gdb server stuff to the gdb
> command line.
Eh? An example, please? I guess it depends what the fork command is
actually _doing_.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-17 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 16:55 Alex Bennee
2003-02-17 17:00 ` Daniel Jacobowitz
2003-02-17 17:14 ` Alex Bennee
2003-02-17 17:27 ` Daniel Jacobowitz [this message]
2003-02-17 17:46 ` Alex Bennee
2003-02-17 17:04 ` 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=20030217172738.GA19524@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kernel-hacker@bennee.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