From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20639 invoked by alias); 18 Jul 2008 20:50:48 -0000 Received: (qmail 20630 invoked by uid 22791); 18 Jul 2008 20:50:47 -0000 X-Spam-Check-By: sourceware.org Received: from aussmtpmrkps320.us.dell.com (HELO aussmtpmrkps320.us.dell.com) (143.166.224.254) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 18 Jul 2008 20:50:27 +0000 X-IronPort-AV: E=Sophos;i="4.31,212,1215406800"; d="scan'208";a="368507091" Received: from unknown (HELO M31.equallogic.com) ([12.110.134.31]) by aussmtpmrkps320.us.dell.com with SMTP; 18 Jul 2008 15:50:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18561.528.278824.732595@gargle.gargle.HOWL> Date: Fri, 18 Jul 2008 21:21:00 -0000 From: Paul Koning To: stanshebs@earthlink.net Cc: gdb@sourceware.org Subject: Re: Towards multiprocess GDB References: <4880FFA8.3080600@earthlink.net> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-07/txt/msg00212.txt.bz2 >>>>> "Stan" == Stan Shebs writes: Stan> When it's time to run, the user will want the ability to run Stan> anywhere from one to all of the programs, each with its own Stan> argument list. It should be possible to do this with a single Stan> command, so that the user isn't scrambling to put in all the Stan> run commands quickly enough. Nice. Do we need a way to specify a different environment for each program? Stan> Implementationwise, we will need to replace the single exec Stan> target with a list of execs, and modify symbol machinery to Stan> support a many-many relationship between programs and symbol Stan> tables. Although my inclination is to create a new symbol table Stan> for each process' image of each shared library, that may be Stan> excessively expensive. Indeed it might be excessive. Avoiding it means adding the notion of per-program offsets, so program A can map library L at offset X, while program B maps that same library at offset Y. Stan> In addition to thoughts on desired user interface, I would Stan> welcome suggestions on how to add this feature incrementally; Stan> the abovementioned bits are a lot to add all at once! You mentioned threads in passing. Those are still needed, so you need to allow multiple programs each of which may have multiple threads. paul