From: Greg Weeks <greg.weeks@timesys.com>
To: Brian Kuschak <bkuschak@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: gdb backtrace with core files
Date: Thu, 07 Apr 2005 13:58:00 -0400 [thread overview]
Message-ID: <425574A8.4030605@timesys.com> (raw)
In-Reply-To: <20050407174454.77209.qmail@web40909.mail.yahoo.com>
Brian Kuschak wrote:
>Is anyone succesfully using gdb for mipsel to debug
>core dumps? If so, can you share your secrets for
>success? I tried various recent versions (6.3,
>6.1.1), but backtrace never works right, even though
>the stack pointer appears to be valid. gdb-5.3
>partially works, but not completely.
>
>Forcing gdb to use a specific stack pointer and PC
>(frame <sp> <pc>) doesn't seem to help either.
>
>Using linux 2.4.25 and gcc 3.3.3.
>
>
>
It appears to work for me. My gdb has a ton of patches from Amit Kale
though. The kernel is the latest malta with a couple of patches that
shouldn't affect gdb.
-bash-2.05b# gdb
GNU gdb TimeSys Linux (6.2.1-1rh)
Copyright 2004 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 "mipsel-linux".
(gdb) file gdb_core_tester
Reading symbols from
/root/TestWare/TTS_2.4.2/command/gdb_man/gdb_core_tester...done.
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) core-file core.2045
Core was generated by `./gdb_core_tester'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libgcc_s.so.1...done.
Loaded symbols for /usr/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 0x00400f48 in add_node (rootptr=0x1000105c, nodeval=193)
at create_core.c:75
75 if(node_ptr->value.value >= nodeval) {
(gdb) bt
#0 0x00400f48 in add_node (rootptr=0x1000105c, nodeval=193)
at create_core.c:75
#1 0x00400fcc in add_node (rootptr=0x10001048, nodeval=193)
at create_core.c:81
#2 0x00400f74 in add_node (rootptr=0x10000140, nodeval=193)
at create_core.c:76
#3 0x00400df8 in create_tree (rootptr=0x10000140) at create_core.c:38
#4 0x00400b4c in main (argc=1, argv=0x7f931b44) at main.c:25
Greg Weeks
next prev parent reply other threads:[~2005-04-07 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 17:44 gdb backtrace with core files Brian Kuschak
2005-04-07 17:53 ` Daniel Jacobowitz
2005-04-07 17:58 ` Greg Weeks [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-07 18:23 Brian Kuschak
2005-04-07 18:27 ` Daniel Jacobowitz
2005-04-07 19:03 Brian Kuschak
2005-04-07 19:08 ` Greg Weeks
2005-04-07 19:38 ` Greg Weeks
2005-04-07 20:43 Brian Kuschak
2005-04-07 20:45 Brian Kuschak
2005-04-08 11:25 ` Greg Weeks
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=425574A8.4030605@timesys.com \
--to=greg.weeks@timesys.com \
--cc=bkuschak@yahoo.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