From: Daniel Jacobowitz <drow@false.org>
To: Andr? P?nitz <apoenitz@trolltech.com>
Cc: gdb@sourceware.org
Subject: Re: How to interpret (encoded?) gdb response
Date: Thu, 14 Aug 2008 20:30:00 -0000 [thread overview]
Message-ID: <20080814150249.GA7601@caradoc.them.org> (raw)
In-Reply-To: <200808141113.21141.apoenitz@trolltech.com>
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:
>
> 67^running
> (gdb)
> &"Cannot access memory at address 0x7fff6ca72a4c\n"
> &"\240\240\354\003\n"
> 67^error,msg="\240\240\354\003"
>
> 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?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-14 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 16:31 André Pönitz
2008-08-14 20:30 ` Daniel Jacobowitz [this message]
2008-08-14 20:39 ` Michael Snyder
2008-08-15 8:49 ` Daniel Jacobowitz
2008-08-15 15:59 ` André Pönitz
2008-08-15 23:28 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080814150249.GA7601@caradoc.them.org \
--to=drow@false.org \
--cc=apoenitz@trolltech.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox