Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: JobHunts02@aol.com
To: gdb@sourceware.org
Subject: Increasing backtrace entries
Date: Thu, 26 Jun 2008 08:00:00 -0000	[thread overview]
Message-ID: <cce.327cfec2.3594a663@aol.com> (raw)

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)


             reply	other threads:[~2008-06-26  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26  8:00 JobHunts02 [this message]
2008-06-26  9:15 ` Andreas Schwab
2008-06-26 18:26   ` Michael Snyder
2008-06-27  6:05 JobHunts02
2008-06-27 17:57 ` Michael Snyder

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=cce.327cfec2.3594a663@aol.com \
    --to=jobhunts02@aol.com \
    --cc=gdb@sourceware.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