From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4444 invoked by alias); 5 Sep 2009 21:15:41 -0000 Received: (qmail 4434 invoked by uid 22791); 5 Sep 2009 21:15:40 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 05 Sep 2009 21:15:35 +0000 Received: (qmail 11563 invoked from network); 5 Sep 2009 21:15:33 -0000 Received: from unknown (HELO orlando) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 5 Sep 2009 21:15:33 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [v4 2/2] multi-executable support Date: Sat, 05 Sep 2009 21:15:00 -0000 User-Agent: KMail/1.9.10 References: <200909030349.38319.pedro@codesourcery.com> <200909051941.12181.pedro@codesourcery.com> <838wgt409z.fsf@gnu.org> In-Reply-To: <838wgt409z.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <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/msg00134.txt.bz2 On Saturday 05 September 2009 21:14:16, Eli Zaretskii wrote: > Here's my question: Why do we need a container for inferiors (that you > call sspace)? I understand why we need a way of starting another > inferior _in_addition_to_ the existing ones (as opposed to > _instead_of_ the existing one). But wouldn't it be enough to have one > command -- "add-inferior", say -- to provide the same set of features > you want, i.e. the ability to debug several inferiors at the same > time? > > 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. 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. We need multiple simultaneous such states. You can actually ignore "info inferiors" if you like. "info programs"/"info sspaces" is basically what you suggest above. (Note that 'add-symbol-space -exec EXEC' and 'close-symbol-space' are just there for convenience. We can live with just 'add-symbol-space'/'add-program', or whatever the spelling is.) -- Pedro Alves