From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10933 invoked by alias); 18 Jun 2008 13:49:20 -0000 Received: (qmail 10919 invoked by uid 22791); 18 Jun 2008 13:49:19 -0000 X-Spam-Check-By: sourceware.org Received: from imr2.ericy.com (HELO imr2.ericy.com) (198.24.6.3) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 18 Jun 2008 13:48:58 +0000 Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m5IDmoT8030064; Wed, 18 Jun 2008 08:48:50 -0500 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jun 2008 08:49:07 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Multiprocess MI extensions Date: Wed, 18 Jun 2008 13:49:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA042911EB@ecamlmw720.eamcs.ericsson.se> In-Reply-To: <200806181238.44911.vladimir@codesourcery.com> From: "Marc Khouzam" To: "Vladimir Prus" Cc: 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-06/txt/msg00181.txt.bz2 > > On another point for multi-process, I was wondering if=20 > there will be a need > > to select a thread-group before issuing commands affecting a entire > > group? Something similar to what we have with -thread-select.=20=20 > > I was thinking that a command affecting a group would apply=20 > to the group > > to which the current thread belongs. > >=20 > > This would allow for any command currently applicable to=20 > the single process > > or inferior, to be applied in the same way. To be honnest,=20 > I'm not entirely > > sure this is a good idea. > >=20 > > Did you guys discuss this? >=20 > Not so much as "discuss". I personally try to avoid=20 > introducing more state in MI, > at all costs. That's why for commands wishing to operate on a=20 > given thread group, > the --thread-group option will be required. Presently, only=20 > -exec-continue and > -exec-interrupt seem to need this, though. There are a couple of enviroment variables that may apply to a given thread-group. I admit that these commands bring up other questions about how to deal with multi-process debugging and that I may be bringing this up a little early. I'll list the commands anyway, but it is just to start the ball rolling (although I'm sure the ball is rolling already :-)) -file-exec-and-symbols (and the like) -exec-arguments (DSF uses '-gdb-set args' instead) -environment-cd -inferior-tty-set (although this can apply to all inferiors as we discussed with Dan in a recent thread) -exec-abort (or kill) The question of exit code also comes up, although I'm not very familiar with it, so I don't know how it applies. This does not look too bad, now that I see it listed :-) Marc