All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Tony Lin <lin.tony@gmail.com>
Cc: ashley jones <ashley_jones_2000@yahoo.com>, linux-mips@linux-mips.org
Subject: Re: Can't debug core files with GDB
Date: Thu, 25 May 2006 22:45:40 -0400	[thread overview]
Message-ID: <20060526024540.GA16815@nevyn.them.org> (raw)
In-Reply-To: <404548f40605251750s2708df73td50a4e9db755408f@mail.gmail.com>

On Thu, May 25, 2006 at 05:50:56PM -0700, Tony Lin wrote:

[2.4]

>       /*
>        * saved cp0 registers
>        */
>       unsigned long cp0_epc;
>       unsigned long cp0_badvaddr;
>       unsigned long cp0_status;
>       unsigned long cp0_cause;

[2.6]

>       /* Saved special registers. */
>       unsigned long cp0_status;
>       unsigned long lo;
>       unsigned long hi;
>       unsigned long cp0_badvaddr;
>       unsigned long cp0_cause;
>       unsigned long cp0_epc;

> Notice how the offsets has changed, no idea why this was done. I
> loaded the core file in the hex dump, and sure enough it is dumped
> with this new ordering.
> 
> I guess gdb is still trying to decode using the old pt_regs format. Is
> it correct to modify gdb to use this new format? Or modify linux to
> output using the old format?

Ralf, do you remember why this changed?  I don't.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-05-26  2:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17  0:02 Can't debug core files with GDB Tony Lin
2006-05-17 13:34 ` Daniel Jacobowitz
2006-05-17 18:39   ` Tony Lin
2006-05-19 13:02     ` Daniel Jacobowitz
2006-05-24  8:14     ` ashley jones
2006-05-25  1:44       ` Tony Lin
2006-05-25  6:05         ` ashley jones
2006-05-25 13:35         ` Daniel Jacobowitz
2006-05-26  0:50           ` Tony Lin
2006-05-26  2:45             ` Daniel Jacobowitz [this message]
2006-05-26 11:39               ` Johannes Stezenbach
2006-05-27  0:21                 ` Tony Lin
2006-05-27  0:45                   ` Daniel Jacobowitz
2006-05-27  0:46                   ` Johannes Stezenbach

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=20060526024540.GA16815@nevyn.them.org \
    --to=dan@debian.org \
    --cc=ashley_jones_2000@yahoo.com \
    --cc=lin.tony@gmail.com \
    --cc=linux-mips@linux-mips.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 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.