From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: [rfc] "reset" / "create-inferior" commands
Date: Wed, 01 Nov 2006 20:28:00 -0000 [thread overview]
Message-ID: <20061101202811.GA20484@nevyn.them.org> (raw)
Some time ago I asked about name choices for a command which would create a
new process, or restart an existing process, without running it. I've
already done the GDB internals work for such a command; the only reason I
haven't added one already is that I couldn't come up with a name.
Here's what it should do:
- When doing native debugging, it should fork and exec the program,
and run until the command shell execs the real program (if necessary).
- When connected to a remote embedded board, it should send the "restart"
packet.
That corresponds in both cases to calling target_create_inferior but not
proceed.
I haven't seen a good name which works for both scenarios. The best idea so
far comes from Paul Brook - if we call the new command "reset", it's
accurate for boards, and not terribly awkward for native processes.
Alternatively, we could add two names for the command which did the same
thing ("create-inferior" or "create-process" as an alias for "reset").
[I would actually have picked "restart" over "reset", but that's taken for
checkpoints. We could still steal it and use "restart checkpoint 1" for
checkpoints, if others think restart is preferable to reset.]
Any comments on this name? I keep wanting the command, so I'd like to find
an acceptable name, and then I can go ahead and implement it.
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2006-11-01 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 20:28 Daniel Jacobowitz [this message]
2006-11-01 20:37 ` Eli Zaretskii
2006-11-02 3:06 ` Joel Brobecker
2006-11-01 22:56 ` Mark Kettenis
2006-11-01 23:06 ` Daniel Jacobowitz
2006-11-02 4:23 ` Eli Zaretskii
2006-11-02 11:53 ` Andrew STUBBS
2006-11-02 13:15 ` Frederic RISS
2006-11-03 17:16 David Anderson
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=20061101202811.GA20484@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.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