From: Daniel Jacobowitz <drow@false.org>
To: Alex Gonzalez <langabe@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Invalid hex digit 59 - Linux MIPS kernel debugging
Date: Fri, 13 Apr 2007 15:09:00 -0000 [thread overview]
Message-ID: <20070413150929.GA20853@caradoc.them.org> (raw)
In-Reply-To: <c58a7a270704130801k3f2db53q7802ccc2be514448@mail.gmail.com>
On Fri, Apr 13, 2007 at 04:01:35PM +0100, Alex Gonzalez wrote:
> Hi,
>
> I am trying to debug the Linux MIPS kernel using gdb.
>
> I have the gdb stub in the kernel and gdb communicating through the
> serial interface, I seem to be able to set a breakpoint but gdb never
> hits it. It complains with a 'Reply contains invalid hex digit 59',
> which I guess refers to the semicolon character used in the response.
>
> I enclose the session output in case someone can give me some pointers.
Try a CVS snapshot of GDB. What's probably going on is that your GDB
expects 64-bit registers, so it is confused to find a semicolon in the
middle of a register value.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-04-13 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 15:01 Alex Gonzalez
2007-04-13 15:09 ` Daniel Jacobowitz [this message]
2007-04-13 16:40 ` Alex Gonzalez
2007-04-13 17:29 ` Daniel Jacobowitz
2007-04-13 17:42 ` Alex Gonzalez
2007-04-13 18:09 ` Daniel Jacobowitz
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=20070413150929.GA20853@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=langabe@gmail.com \
/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