* RE: GDB 6.0 backtrace limit to only 3 lines
@ 2004-09-10 2:48 Reschke Benjamin-A16256
2004-09-10 8:03 ` Mark Kettenis
0 siblings, 1 reply; 5+ messages in thread
From: Reschke Benjamin-A16256 @ 2004-09-10 2:48 UTC (permalink / raw)
To: gdb
>
> > 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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: GDB 6.0 backtrace limit to only 3 lines
2004-09-10 2:48 GDB 6.0 backtrace limit to only 3 lines Reschke Benjamin-A16256
@ 2004-09-10 8:03 ` Mark Kettenis
2004-09-10 15:17 ` Daniel Jacobowitz
0 siblings, 1 reply; 5+ messages in thread
From: Mark Kettenis @ 2004-09-10 8:03 UTC (permalink / raw)
To: Benjamin.Reschke; +Cc: gdb
From: Reschke Benjamin-A16256 <Benjamin.Reschke@motorola.com>
Date: Fri, 10 Sep 2004 12:18:31 +0930
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:
What version of GCC are you using? AFAIK no version of GCC should
generate DW_EH_PE_indirect encodings, but apparently it (or something
else) does.
Mark
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: GDB 6.0 backtrace limit to only 3 lines
2004-09-10 8:03 ` Mark Kettenis
@ 2004-09-10 15:17 ` Daniel Jacobowitz
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Jacobowitz @ 2004-09-10 15:17 UTC (permalink / raw)
To: Mark Kettenis; +Cc: Benjamin.Reschke, gdb
On Fri, Sep 10, 2004 at 10:03:04AM +0200, Mark Kettenis wrote:
> From: Reschke Benjamin-A16256 <Benjamin.Reschke@motorola.com>
> Date: Fri, 10 Sep 2004 12:18:31 +0930
>
> 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:
>
> What version of GCC are you using? AFAIK no version of GCC should
> generate DW_EH_PE_indirect encodings, but apparently it (or something
> else) does.
If assembler and linker properly support .uaword %r_disp32(foo),
then use PC relative 32-bit relocations instead of absolute relocs
for shared libraries. On sparc64, use pc relative 32-bit relocs even
for binaries, to save memory.
From config/sparc/sparc.h; DW_EH_PE_indirect is used. A couple of
other targets generate it also, f.ex. i386-solaris2.
--
Daniel Jacobowitz
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: GDB 6.0 backtrace limit to only 3 lines
2004-09-09 0:51 Reschke Benjamin-A16256
@ 2004-09-09 3:09 ` Joel Brobecker
0 siblings, 0 replies; 5+ messages in thread
From: Joel Brobecker @ 2004-09-09 3:09 UTC (permalink / raw)
To: Reschke Benjamin-A16256; +Cc: 'gdb@sources.redhat.com'
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* GDB 6.0 backtrace limit to only 3 lines
@ 2004-09-09 0:51 Reschke Benjamin-A16256
2004-09-09 3:09 ` Joel Brobecker
0 siblings, 1 reply; 5+ messages in thread
From: Reschke Benjamin-A16256 @ 2004-09-09 0:51 UTC (permalink / raw)
To: 'gdb@sources.redhat.com'
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?
TIA
Ben
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-09-10 15:17 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-09-10 2:48 GDB 6.0 backtrace limit to only 3 lines Reschke Benjamin-A16256
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox