From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Eli Zaretskii <eliz@gnu.org>,
mark.kettenis@xs4all.nl, brobecker@adacore.com,
gdb-patches@sourceware.org
Subject: Re: [patch] Forbid run with a core file loaded
Date: Tue, 08 Jun 2010 02:33:00 -0000 [thread overview]
Message-ID: <m3hblemeyq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201006071220.58289.pedro@codesourcery.com> (Pedro Alves's message of "Mon, 7 Jun 2010 12:20:57 +0100")
Jan> I hope you agree the target stack should be made specific for each
Jan> inferior.
Pedro> I've gone back and forth on that for a while with the multi-exec
Pedro> work. It's trickier than that.
How else would you propose letting people attach to multiple inferiors
using multiple targets? This seems like a reasonable thing to want to
do, e.g., debugging a distributed application of some kind.
Pedro> Consider the extended-remote target --- if you do "add-inferior;
Pedro> <inf 2 created>; inferior 2; run", if we simply had a target
Pedro> stack per inferior, then when you get to "run", you'd only have
Pedro> "exec" on the inferior 2's stack, but you wanted extended-remote
Pedro> to handle creating the inferior.
I don't really know enough about the target API, but this seems fixable.
"Target stack per inferior" does not necessarily imply that the targets
cannot be shared, just that conceptually each inferior carries its own.
Tom
next prev parent reply other threads:[~2010-06-08 2:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:47 Jan Kratochvil
2010-05-21 15:02 ` Mark Kettenis
2010-05-21 15:05 ` Pedro Alves
2010-05-21 15:54 ` Mark Kettenis
2010-05-21 16:08 ` Pedro Alves
2010-05-21 15:05 ` Joel Brobecker
2010-05-21 15:40 ` Mark Kettenis
2010-05-23 19:38 ` Jan Kratochvil
2010-05-23 21:08 ` Eli Zaretskii
2010-06-06 19:51 ` Jan Kratochvil
2010-06-06 23:08 ` Eli Zaretskii
2010-06-07 11:21 ` Pedro Alves
2010-06-08 2:33 ` Tom Tromey [this message]
2010-06-08 11:03 ` Pedro Alves
2010-07-08 17:17 ` Jan Kratochvil
2010-07-08 18:28 ` Eli Zaretskii
2010-07-19 18:02 ` Jan Kratochvil
2010-07-19 18:05 ` Eli Zaretskii
2010-07-19 18:16 ` Jan Kratochvil
2010-07-27 16:00 ` Joel Brobecker
2010-07-19 14:37 ` Pedro Alves
2010-05-23 21:16 ` Pedro Alves
2010-05-21 15:07 ` Jan Kratochvil
2010-05-21 15:04 ` Joel Brobecker
2010-05-21 15:06 ` Pedro Alves
2010-05-21 15:15 ` Joel Brobecker
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=m3hblemeyq.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=pedro@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).