From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [v4 2/2] multi-executable support
Date: Sun, 06 Sep 2009 03:16:00 -0000 [thread overview]
Message-ID: <837hwc4ven.fsf@gnu.org> (raw)
In-Reply-To: <200909052215.32972.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Sat, 5 Sep 2009 22:15:32 +0100
>
> > IOW, I don't understand why we need to group inferiors by sspaces.
>
> I don't see how to model vfork (in the shared region) (, or DICOS)
> with just that. To the extreme, if you load a shared library in
> a vfork child, the parent ends up with it loaded too.
Sorry, I don't understand this problem. Could you elaborate, please?
> Note that the current GDB model is that inferiors only exist
> after a "run", that is, inferior ~= process. Before "run",
> there's no inferior, "info inferiors" is empty, yet, you
> have a program loaded already.
That's the underlying technicality. From user perspective, we could
certainly think that the inferior ``exists'' as soon as there's a
possibility to issue the `file' command without replacing the
already existing inferiors.
> We need multiple simultaneous such states.
Which states?
next prev parent reply other threads:[~2009-09-06 3:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 2:49 [v4 0/2] " Pedro Alves
2009-09-03 2:51 ` [v4 1/2] " Pedro Alves
2009-09-03 2:53 ` [v4 2/2] " Pedro Alves
2009-09-03 18:31 ` Eli Zaretskii
2009-09-03 18:40 ` Pedro Alves
2009-09-03 20:37 ` Eli Zaretskii
2009-09-05 18:41 ` Pedro Alves
2009-09-05 20:16 ` Eli Zaretskii
2009-09-05 21:15 ` Pedro Alves
2009-09-06 3:16 ` Eli Zaretskii [this message]
2009-09-08 15:16 ` [v4 2/2] multi-executable support (new v5 patch included) Pedro Alves
2009-09-08 19:16 ` Eli Zaretskii
2009-10-05 15:22 ` Pedro Alves
2009-09-09 6:40 ` Vladimir Prus
2009-09-09 10:28 ` Pedro Alves
2009-09-03 2:56 ` [v4 0/2] multi-executable support (.gz) Pedro Alves
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=837hwc4ven.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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