This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Increasing backtrace entries
- From: JobHunts02 at aol dot com
- To: gdb at sourceware dot org
- Date: Thu, 26 Jun 2008 03:59:31 EDT
- Subject: Increasing backtrace entries
When I run gdb on a core dump after my application crashes, my backtrace
consists of only 1 entry (see below). Is there a way to increase the number of
entries in the backtrace so I can determine how I got to this point? Does
only getting 1 entry in the trace indicate something?
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<_http://gnu.org/licenses/gpl.html_ (http://gnu.org/licenses/gpl.html) >
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu
--target=powerpc-linux"...
warning: exec file is newer than core file.
Cannot access memory at address 0x6d61706c
(gdb) bt
#0 0x1003cc60 in wsrFind (
reg_p=0x30284d9e <Address 0x30284d9e out of bounds>, rxc=-1)
at lwc.c:4024
Cannot access memory at address 0x30284d84
(gdb)
**************Gas prices getting you down? Search AOL Autos for
fuel-efficient used cars. (http://autos.aol.com/used?ncid=aolaut00050000000007)