From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11683 invoked by alias); 5 Jun 2008 13:18:50 -0000 Received: (qmail 11659 invoked by uid 22791); 5 Jun 2008 13:18:49 -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; Thu, 05 Jun 2008 13:18:28 +0000 Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m55DILrC003851; Thu, 5 Jun 2008 08:18:21 -0500 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 5 Jun 2008 08:18:21 -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: RE: non-stop and current thread exiting Date: Thu, 05 Jun 2008 13:18:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA0429117A@ecamlmw720.eamcs.ericsson.se> In-Reply-To: A From: "Marc Khouzam" To: "Vladimir Prus" , 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/msg00027.txt.bz2 > What I was thinking if that if you select a thread, and continue it, > and the thread exits, it would be more user-friendly to gray this > thread, add "(exited)" and then retire it next time we stop.=20 That is an interesting idea. As all UI ideas, its value will be determined in actual usage. But it may be nice to have this option. > You are right that some frontend changes will be required -- but they > are required anyway to show the "running" state of the thread, so > seems the extra change to show "exited" state does not add much > complexity. If the output of thread-list-ids is simply augmented with (exited), you are right that it would be an easy change for a frontend. >=20 > > In the case of b) or c) one point that is important for the > > a frontend is how GDB will react to prohibited commands > > when no thread is selected? Will a prohibited command > > cause an ^error or maybe an empty ^done, or something else? >=20 > With (b), you always have some thread selected. When it is actually > exited thread, I'd say ^error is the best way. If you send a command > and get empty ^done, while you expect some data in the response, it's > not very good, I think. Sounds right.