From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12055 invoked by alias); 6 Sep 2009 03:16:16 -0000 Received: (qmail 12043 invoked by uid 22791); 6 Sep 2009 03:16:15 -0000 X-SWARE-Spam-Status: No, hits=-0.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_JMF_BL,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout2.012.net.il (HELO mtaout2.012.net.il) (84.95.2.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 06 Sep 2009 03:16:09 +0000 Received: from conversion-daemon.i_mtaout2.012.net.il by i_mtaout2.012.net.il (HyperSendmail v2004.12) id <0KPJ001004OT4S00@i_mtaout2.012.net.il> for gdb-patches@sourceware.org; Sun, 06 Sep 2009 06:16:06 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.50.163]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KPJ004Q652T4TB0@i_mtaout2.012.net.il>; Sun, 06 Sep 2009 06:16:06 +0300 (IDT) Date: Sun, 06 Sep 2009 03:16:00 -0000 From: Eli Zaretskii Subject: Re: [v4 2/2] multi-executable support In-reply-to: <200909052215.32972.pedro@codesourcery.com> To: Pedro Alves Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <837hwc4ven.fsf@gnu.org> References: <200909030349.38319.pedro@codesourcery.com> <200909051941.12181.pedro@codesourcery.com> <838wgt409z.fsf@gnu.org> <200909052215.32972.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00139.txt.bz2 > From: Pedro Alves > 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?