This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Colors in gdb

From: Tom Tromey <tromey at redhat dot com>
To: Kevin Pouget <kevin dot pouget at gmail dot com>
Cc: Surya Kiran Gullapalli <suryakiran dot gullapalli at gmail dot com>, gdb at sourceware dot org
Date: Tue, 15 Jan 2013 12:02:20 -0700
Subject: Re: Colors in gdb
References: <CAKkRBO3cmUb44HsKcS-esECgs8HFozz4jmnNDcA-b=wLP5v6_g@mail.gmail.com> <87fw22jq1g.fsf@fleche.redhat.com> <CAPftXUJ1tvJVmTmHNfME9t_3u8tQMv_ioDm7iLcxbDtkZ_v6=A@mail.gmail.com>

>>>>> "Kevin" == Kevin Pouget <kevin.pouget@gmail.com> writes:

Kevin> I have colors in my gdb Python prompt since quite a while, I wonder
Kevin> what could be different in the context of prompt printing and pretty
Kevin> printing ?

For ordinary printing, there's just no place to hook into gdb.

For printing via Python pretty-printers, strings are further processed
by gdb before printing, and in particular the escape sequences are
turned into plain text.


For backtraces it could be done by writing one's own "bt" in Python.  I
vaguely recall that somebody did this once.

Tom

Follow-Ups:
- Re: Colors in gdb
  - From: Matt Rice

References:
- Colors in gdb
  - From: Surya Kiran Gullapalli
- Re: Colors in gdb
  - From: Tom Tromey
- Re: Colors in gdb
  - From: Kevin Pouget

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]