Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Alex Gonzalez" <langabe@gmail.com>
To: "Alex Gonzalez" <langabe@gmail.com>, gdb@sourceware.org
Subject: Re: Invalid hex digit 59 - Linux MIPS kernel debugging
Date: Fri, 13 Apr 2007 17:42:00 -0000	[thread overview]
Message-ID: <c58a7a270704131042h3b0ae158u5f87f923c6440b00@mail.gmail.com> (raw)
In-Reply-To: <20070413172923.GA26847@caradoc.them.org>

Thanks a lot, that was very helpful.

Setting the architecture to mips:isa32 indeed works. And you're right
in that the 32bits kernel is running on an RM9000 with 64 bits
architecture.

Will the CVS version work without having to set the architecture or
will I still have to do so?

Regards,
Alex

On 4/13/07, Daniel Jacobowitz <drow@false.org> wrote:
> On Fri, Apr 13, 2007 at 05:40:25PM +0100, Alex Gonzalez wrote:
> > Thanks, I'll try that.
> >
> > If you don't mind me asking, why would gdb expect 64bits registers
> > when the target abi is set to o32?
>
> Because you can run o32 binaries on hardware with 64-bit registers,
> and there are some ugly corner cases where the upper half of registers
> can cause problems - e.g. for things which have undefined behavior if
> the input registers are not correctly sign extended.  You've probably
> built a 32-bit kernel for a processor that GDB knows is actually
> 64-bit.  But if your debug agent only supplies 32 bits, then GDB will
> get along fine (once it knows that).
>
> If you don't want to change GDB versions, an appropriate "set arch"
> might work - but I recommend the current snapshots.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>


  reply	other threads:[~2007-04-13 17:42 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
2007-04-13 16:40   ` Alex Gonzalez
2007-04-13 17:29     ` Daniel Jacobowitz
2007-04-13 17:42       ` Alex Gonzalez [this message]
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=c58a7a270704131042h3b0ae158u5f87f923c6440b00@mail.gmail.com \
    --to=langabe@gmail.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