From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-31809-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 27700 invoked by alias); 2 May 2008 17:36:16 -0000
Received: (qmail 27688 invoked by uid 22791); 2 May 2008 17:36:15 -0000
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 02 May 2008 17:35:45 +0000
Received: (qmail 7633 invoked from network); 2 May 2008 17:35:43 -0000
Received: from unknown (HELO localhost) (vladimir@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 2 May 2008 17:35:43 -0000
From: Vladimir Prus <vladimir@codesourcery.com>
To: Pawel Piech <pawel.piech@windriver.com>
Subject: Re: MI non-stop interface details
Date: Fri, 02 May 2008 17:36:00 -0000
User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405)
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,  Pedro Alves <pedro@codesourcery.com>,  gdb@sourceware.org
References: <6D19CA8D71C89C43A057926FE0D4ADAA042910AB@ecamlmw720.eamcs.ericsson.se> <200805022113.13214.vladimir@codesourcery.com> <481B4FDC.4010802@windriver.com>
In-Reply-To: <481B4FDC.4010802@windriver.com>
MIME-Version: 1.0
Content-Type: text/plain;   charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200805022135.39862.vladimir@codesourcery.com>
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-05/txt/msg00027.txt.bz2

On Friday 02 May 2008 21:31:08 Pawel Piech wrote:

> Right now, *stopped reports the thread which hit the breakpoint. In
> all-stop mode, all threads are stopped. In non-stop mode, only that thread
> is stopped.
>=20
> We surely can add an extra field to indicate which threads are actually s=
topped,
> if this makes life easier.
>=20=20=20
>  Thank You :-)=C2=A0 It would be more helpful if the thread-id field was=
=20
>  left alone and always reported the triggering thread as it does now.=C2=
=A0=20
>  It would be better (more consistent and logical) if the new field=20
>  was used to indicate whether or not the whole container changed state.=
=20=20=20=20

For avoidance of doubt, do you have any objections to *running using the "t=
hread-id"
as the field name? Since this is new notification, there's no backward comp=
atibility
issues, and there's no issue of which thread originally triggered anything.

- Volodya