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: [python] Pretty-printers and addressprint

From: Tom Tromey <tromey at redhat dot com>
To: AndrÃ PÃnitz <andre dot poenitz at nokia dot com>
Cc: gdb at sourceware dot org
Date: Tue, 10 Nov 2009 08:14:49 -0700
Subject: Re: [python] Pretty-printers and addressprint
References: <20091110021158.C3C2576D70@ppluzhnikov.mtv.corp.google.com> <8ac60eac0911100006yc31e2acmba7bf9fde33ddfa@mail.gmail.com> <4AF92621.4080807@redhat.com> <200911101021.47431.andre.poenitz@nokia.com>
Reply-to: tromey at redhat dot com

>>>>> "AndrÃ" == AndrÃ PÃnitz <andre.poenitz@nokia.com> writes:

AndrÃ> That would be useful in my opinion. Even if the proper encoding were 
AndrÃ> known, data could still be corrupted. Getting direct access to the
AndrÃ> real data would be nice, even though it is already possible right 
AndrÃ> now using 'manual' iteration the data using a "char *" value.

The branch in the archer repository has some memory-reading functions in
the Python API that should be useful for accessing the raw bits.
Those are probably reasonably ready for pushing into CVS -- Thiago is
the real expert here, maybe he could say.

Tom

References:
- [python] Pretty-printers and addressprint
  - From: Paul Pluzhnikov
- Re: [python] Pretty-printers and addressprint
  - From: Paul Pluzhnikov
- Re: [python] Pretty-printers and addressprint
  - From: Phil Muldoon
- Re: [python] Pretty-printers and addressprint
  - From: André Pönitz

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