From: Alex Bennee <kernel-hacker@bennee.com>
To: gdb@sources.redhat.com
Subject: What has replaced fork to launch external commands?
Date: Mon, 17 Feb 2003 16:55:00 -0000 [thread overview]
Message-ID: <1045500565.2505.20.camel@cambridge.braddahead> (raw)
I thought I would give the latest gdb(5.3) a spin and see if it could
interface with ST's gdb server to talk to my ICE. The original gcc is
dated 20020211.
Happy that it all built ok for my target system it fell over on startup
because the "fork" command used to lauch the gdbserver seems to of
disapeared:
fork shlaunch -si $arg0 -gdbserv host=$arg1 -cid0 host=$arg1
noposixconsole
Is there a drop-in replacement? I greped the Changelogs but all the fork
references seem to be talking about debugged processes rather than
commands.
--
Alex, homepage: http://www.bennee.com/~alex/
"I'm a cat person, myself," she said, vaguely. A low-level voice said:
"Yeah? Yeah? Wash in your own spit, do you?"
-- It's a dog's life
(Terry Pratchett, Moving Pictures)
next reply other threads:[~2003-02-17 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 16:55 Alex Bennee [this message]
2003-02-17 17:00 ` Daniel Jacobowitz
2003-02-17 17:14 ` Alex Bennee
2003-02-17 17:27 ` Daniel Jacobowitz
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=1045500565.2505.20.camel@cambridge.braddahead \
--to=kernel-hacker@bennee.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