This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

backtrace showing incorrect information in Solaris


Hi,

I'm having a problem in backtracing coredumps with gdb 5.3
I'm working on Solaris platform platform (SunOs 5.9) and I'm using
gcc 3.2.3 configured with following options,

/usr/local/lib/gcc-lib/sparc-sun-solaris2.9/3.2.3/specs
Configured with: ../configure --disable-nls --with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as
Thread model: posix
gcc version 3.2.3


I'm trying to backtrace a coredump generated by a multi-threaded application compiled with following compile flags,

compile options - -ggdb -Wall -D _REENTRENT

I get the following backtrace, however frame 3 onwards seems to be incorrect

(gdb) bt
#0  0xfe69c7d0 in _poll () from /usr/lib/libc.so.1
#1  0xfe64e738 in _select () from /usr/lib/libc.so.1
#2  0xfe58ec84 in select () from /usr/lib/libthread.so.1
#3  0x001d8e64 in vtable for std::out_of_range ()
#4  0x001ce918 in vtable for std::out_of_range ()
#5  0x000da694 in std::length_error::length_error(std::string const&) ()
#6  0x000cdacc in typeinfo for short* ()

Earlier I used gcc 2.95.3 with gdb 5.0 in the same environment and did not have any problem.

thanks

Dhammika

Attachment: Disclaimer_Message.txt
Description: Text document


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]