This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [v4 2/2] multi-executable support
> 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?