From: Daniel Jacobowitz <dan@debian.org>
To: Tony Lin <lin.tony@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Can't debug core files with GDB
Date: Wed, 17 May 2006 09:34:02 -0400 [thread overview]
Message-ID: <20060517133402.GA2480@nevyn.them.org> (raw)
In-Reply-To: <404548f40605161702y199c34a5wa89ec5f84cdeee09@mail.gmail.com>
On Tue, May 16, 2006 at 05:02:35PM -0700, Tony Lin wrote:
> When I force a core file and try to debug it, I get empty values:
>
> >./gdb ./nebtest ./core.524.nebtest
>
> GNU gdb 6.4
> Copyright 2005 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "mips-linux"...Using host libthread_db
> library "/lib/libthread_db.so.1".
>
> Core was generated by `./nebtest'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /lib/libgcc_s.so.1...done.
> Loaded symbols for /lib/libgcc_s.so.1
> Reading symbols from /lib/libc.so.6...done.
> Loaded symbols for /lib/libc.so.6
> Reading symbols from /lib/ld.so.1...done.
> Loaded symbols for /lib/ld.so.1
> #0 0x00000000 in ?? ()
> (gdb) bt
> #0 0x00000000 in ?? ()
> #1 0x00000000 in ?? ()
Check the contents of the core file with objdump? I recall seeing at
least one recent MIPS kernel which failed to save registers. Take a
look at the .reg section.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-17 13:34 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 [this message]
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
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=20060517133402.GA2480@nevyn.them.org \
--to=dan@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox