From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-31771-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 22879 invoked by alias); 29 Apr 2008 18:51:22 -0000
Received: (qmail 22828 invoked by uid 22791); 29 Apr 2008 18:51:20 -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; Tue, 29 Apr 2008 18:50:49 +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 m3TIodS0024518; 	Tue, 29 Apr 2008 13:50:39 -0500
Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 	 Tue, 29 Apr 2008 13:50:37 -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: MI non-stop interface details
Date: Wed, 30 Apr 2008 07:18:00 -0000
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA042910AA@ecamlmw720.eamcs.ericsson.se>
In-Reply-To: <200804262034.00245.vladimir@codesourcery.com>
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Vladimir Prus" <vladimir@codesourcery.com>, "Doug Evans" <dje@google.com>
Cc: <gdb@sourceware.org>, "Pawel Piech" <pawel.piech@windriver.com>
X-IsSubscribed: yes
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-04/txt/msg00253.txt.bz2


> >   - CLI users won't see the thread switches
> >=20
> > IOW GDB won't switch the current thread on the user, right?  [just
> > want to understand what you're saying, not to suggest a preference,
> > per se]
>=20
> Yes. GDB will switch its internal "current thread" when processing event,
> but it will switch it back to whatever user has last set before processing
> next user command.

I think this is great.

> > 5. Introduce new command -query-feature   (?) [assuming it's not there
> > already, I don't know]
>
> That will report if a feature is enabled or not? We don't have it (just l=
ike=20
> we don't have -enable-feature yet). I'm thinking, though, that for all fe=
atures=20
> we'd document if it's enabled by default, or not, so this command might n=
ot be=20
> a big use.

You may be right that such a command may not prove very useful, but in my e=
xperience,
if you can modify a setting, it is always good to have a way to report its =
current state.