All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Pete Popov <ppopov@embeddedalley.com>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: gdb/kgdb register mismatch
Date: Thu, 23 Feb 2006 16:31:24 -0500	[thread overview]
Message-ID: <20060223213124.GA3638@nevyn.them.org> (raw)
In-Reply-To: <1140723606.11388.321.camel@localhost.localdomain>

On Thu, Feb 23, 2006 at 11:40:06AM -0800, Pete Popov wrote:
> 
> I'm having the following problems with gdb/kgdb:
> 
> 64bit CPU, running a 32 bit kernel. When I break at a certain point, I
> can see that the kernel kgdb stub appears to be sending the correct
> register information, where each reg value written in the kgdb packet is
> 32bit. However, the cross gdb client seems to be interpreting, or
> expecting, 64bit register values so it 'skips' over every other value.
> For example:
> 
> reg values sent by kgdb:      reg values shown by gdb client:
> reg 0:  0x00000000            reg0:  0x00000001
> reg 1:  0x00000001            reg1:  0x00000002
> reg 2:  0x00000002            reg2:  0x00000004
> reg 3:  0x00000003
> reg 4:  0x00000004
> 
> Should the kgdb stub be sending 64bit values for the registers, even
> though it's a 32bit kernel?  If the stub is supposed to be sending 32bit
> register values, any suggestion why cross gdb is not interpreting them
> correctly?

This is a FAQ; it's a bug in GDB that will be fixed someday, but for
now use "set architecture mips:isa32".

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-02-23 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 19:40 gdb/kgdb register mismatch Pete Popov
2006-02-23 21:31 ` Daniel Jacobowitz [this message]
2006-02-23 21:58   ` Pete Popov

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=20060223213124.GA3638@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ppopov@embeddedalley.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.