From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5677 invoked by alias); 15 Jan 2009 13:59:48 -0000 Received: (qmail 5666 invoked by uid 22791); 15 Jan 2009 13:59:46 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 15 Jan 2009 13:59:10 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E69F72A96D5; Thu, 15 Jan 2009 08:59:08 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id w+GXyxYAsfPO; Thu, 15 Jan 2009 08:59:08 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 5090C2A96CC; Thu, 15 Jan 2009 08:59:08 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 6275CE7ACD; Thu, 15 Jan 2009 17:59:01 +0400 (RET) Date: Thu, 15 Jan 2009 13:59:00 -0000 From: Joel Brobecker To: Pierre Muller Cc: gdb-patches@sourceware.org, 'Pedro Alves' Subject: Re: [BUG] Quit and "(running)" problem Message-ID: <20090115135901.GI24105@adacore.com> References: <000001c9770e$5579c160$006d4420$@u-strasbg.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c9770e$5579c160$006d4420$@u-strasbg.fr> User-Agent: Mutt/1.4.2.2i 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-01/txt/msg00353.txt.bz2 > (top-gdb) set height 1 > (top-gdb) n > ---Type to continue, or q to quit---q > Quit > (top-gdb) set height 80 > (top-gdb) inf thr > 2 Thread 3768.0xb0 (running) > * 1 Thread 3768.0xd98 (running) > (top-gdb) cont > Continuing. > Cannot execute this command while the selected thread is running. Ugh! :-( > This needs a fix! Right, I agree, and I think we should try to fix it before we release. Would you mind creating a PR in our database? I'll reference it in our checklist for the next release. Thanks, -- Joel