From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-33837-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 18008 invoked by alias); 24 Feb 2009 19:09:28 -0000
Received: (qmail 17998 invoked by uid 22791); 24 Feb 2009 19:09:27 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 24 Feb 2009 19:09:20 +0000
Received: (qmail 12267 invoked from network); 24 Feb 2009 19:09:18 -0000
Received: from unknown (HELO orlando) (pedro@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 24 Feb 2009 19:09:18 -0000
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Subject: Re: More descriptive prompt [was Re: Process exit in multi-process, and  gdb's selected thread.]
Date: Tue, 24 Feb 2009 19:09:00 -0000
User-Agent: KMail/1.9.10
Cc: Doug Evans <dje@google.com>,  Marc Khouzam <marc.khouzam@ericsson.com>
References: <e394668d0902241012n458775c5s9e7ba9187209764@mail.gmail.com> <200902241841.11813.pedro@codesourcery.com>
In-Reply-To: <200902241841.11813.pedro@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain;   charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200902241909.16678.pedro@codesourcery.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: 2009-02/txt/msg00154.txt.bz2

On Tuesday 24 February 2009 18:41:11, Pedro Alves wrote:
> On Tuesday 24 February 2009 18:12:03, Doug Evans wrote:
> > If there's general favorability of this I'll work on a patch.

To be clear, I meant to say that I do favor a way to have a
more descriptive prompt, however it ends up implemented.  I'd be
fine with python, or whatever.

> This was something that had occured to be before as well when
> I got tired of doing "info threads" while working on non-stop. 
> 
> This is what I was using at one point.  It added a PS1 style
> formatting to the gdb command, so I could do
> 
> (gdb) set prompt (\\p \\T: \\S)
> 
> And have the prompt show up as:
> 
>  (1 Thread 0x7ffff7fd36e0 (LWP 12690): stopped) 
> 
> or, ...
> 
>  (1 Thread 0x7ffff7fd36e0 (LWP 12690): running) 
> 
> etc.
> 

-- 
Pedro Alves