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 09:35:29 -0400 [thread overview]
Message-ID: <20060525133529.GA31379@nevyn.them.org> (raw)
In-Reply-To: <404548f40605241844y41b897b6sb8a7512feb8655f6@mail.gmail.com>
On Wed, May 24, 2006 at 06:44:26PM -0700, Tony Lin wrote:
> I've pretty much concluded the gdb is not at fault. Loading a coredump
> generated by another mips-linux system, it was able to read the
> registers correctly and lookup the program counter.
>
> So the problem now is my 32-bit mips-linux is generating core files in
> a different format than what gdb expects. I've been digging into
> fs/exec.c and fs/binfmt_elf.c without much success. Are there
> documents describing the expected coredump header format?
No. But...
> I'm not really familiar with the register terminology (fpu? xfpregs?)
> so am having some trouble figuring out where linux write the program
> counter into the core dump.
Take a look at asm-mips/elf.h and IIRC arch/mips/kernel/process.c. Or,
trace the macros through binfmt_elf.c, where it creates NOTE sections.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-25 13:35 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 [this message]
2006-05-26 0:50 ` Tony Lin
2006-05-26 2:45 ` Daniel Jacobowitz
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=20060525133529.GA31379@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.