From: Reschke Benjamin-A16256 <Benjamin.Reschke@motorola.com>
To: gdb@sources.redhat.com
Subject: RE: GDB 6.0 backtrace limit to only 3 lines
Date: Fri, 10 Sep 2004 02:48:00 -0000 [thread overview]
Message-ID: <643810D0E0F1144C8F9D798CF5294DD80244C0F7@zas24exm01.corp.mot.com> (raw)
>
> > I recently downloaded and compiled GDB 6.0 for Sparc Solaris 8 and it
> > seems that whenever I issue the "backtrace" command it will only ever
> > print out 3 lines. No more, no less. Is there an option or setting
> > that I need to configure when compiling the tool. Or after compilation
> > is there a setting or option I need to set?
>
> I would try 6.2.1. IIRC, there were some known issues on sparc-solaris
> with 6.0.
>
> --
> Joel
So I downloaded an compiled GDB 6.2 and now I receive the follow output when I run gdb with my exe and core file:
------
%> gdb myExe.exe core
GNU gdb 6.2
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 "sparc-sun-solaris2.8"...
/home/elixir/temp/gdb-6.2/gdb/dwarf2-frame.c:1071: internal-error: Unsupported encoding: DW_EH_PE_indirect
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
/home/elixir/temp/gdb-6.2/gdb/dwarf2-frame.c:1071: internal-error: Unsupported encoding: DW_EH_PE_indirect
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
------
Any ideas what is causing this? I also compiled it for Linux and had no problems whatsoever.
next reply other threads:[~2004-09-10 2:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 2:48 Reschke Benjamin-A16256 [this message]
2004-09-10 8:03 ` Mark Kettenis
2004-09-10 15:17 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2004-09-09 0:51 Reschke Benjamin-A16256
2004-09-09 3:09 ` Joel Brobecker
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=643810D0E0F1144C8F9D798CF5294DD80244C0F7@zas24exm01.corp.mot.com \
--to=benjamin.reschke@motorola.com \
--cc=gdb@sources.redhat.com \
/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