This is the mail archive of the
mailing list for the GDB project.
Re: How to interpret (encoded?) gdb response
- From: Daniel Jacobowitz <drow at false dot org>
- To: Andr? P?nitz <apoenitz at trolltech dot com>
- Cc: gdb at sourceware dot org
- Date: Thu, 14 Aug 2008 11:02:49 -0400
- Subject: Re: How to interpret (encoded?) gdb response
- References: <firstname.lastname@example.org>
On Thu, Aug 14, 2008 at 11:13:08AM +0200, Andr? P?nitz wrote:
> Hi all.
> I do the foillowing:
> - run an inferior containing a tight endless loop
> - attach to it with gdb -pid=<id>
> - run 'kill <pid>' in shell
> - do -exec-continue
> then I get:
> &"Cannot access memory at address 0x7fff6ca72a4c\n"
> Does that msg have any meaning, i.e. how would I "decode" it?
> The message appears also in a non-MI environment, but is even
> less legible there...
No, it's some sort of bug or bad pointer. Does this happen in HEAD?