From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7609 invoked by alias); 5 Jun 2009 18:42:05 -0000 Received: (qmail 7592 invoked by uid 22791); 5 Jun 2009 18:42:04 -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 imr1.ericy.com (HELO imr1.ericy.com) (198.24.6.9) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Jun 2009 18:41:58 +0000 Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n55IrD13031104; Fri, 5 Jun 2009 13:53:17 -0500 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 5 Jun 2009 13:41:49 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: Re: [MI][Patch] -exec-continue/interrupt --thread-group expects wrong id Date: Fri, 05 Jun 2009 18:42:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA0789E27E@ecamlmw720.eamcs.ericsson.se> In-Reply-To: A References: <6D19CA8D71C89C43A057926FE0D4ADAA0789E1B2@ecamlmw720.eamcs.ericsson.se> A From: "Marc Khouzam" To: "Vladimir Prus" , 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-06/txt/msg00109.txt.bz2 =20 > -----Original Message----- > From: gdb-patches-owner@sourceware.org=20 > [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Vladimir Prus > Sent: June-05-09 2:36 PM > To: gdb-patches@sources.redhat.com > Subject: Re: [MI][Patch] -exec-continue/interrupt=20 > --thread-group expects wrong id >=20 > Marc Khouzam wrote: >=20 > > Hi, > >=20 > > After Pedro kindly pointed out that there is a > > --thread-group parameter to -exec-continue and -exec-interrupt > > (how did I miss that?) I tried them out. > > I found that they still expect the old form of the > > threadGroupId (starting with a 'p'). > >=20 > > The patch below fixes both methods. > >=20 > > This is hard to test since HEAD does not have a fully functional > > multi-process, but I was able to confirm that the threadGroupId > > gets properly accepted with my patch. >=20 > Thanks, I have applied this patch as attached. Please include=20 > changelog > entry for future patch submissions though -- somebody still=20 > has to write > them before "cvs commit" :-) Woops, I forgot about the ChangeLog. Thanks for applying!