--- Comment #7 from kev dot gilbert at cdu dot edu dot au 2005-11-01 23:55
---
I've just had a look at gdb PR 2024 and disagree with the comment "backtrace
fails when function ends with call to abort". The following code also ehibits
the problem noted here.
=
--- Comment #3 from kev dot gilbert at cdu dot edu dot au 2005-10-23 22:13
---
Just for the record, I've pasted the incorrect gdb output for the second
backtrace. It is as follows:
#0 0x00240402 in __kernel_vsyscall ()
#1 0x00726118 in raise () from /lib/libc.so.6
#2 0x007278
base for "main".) at
test.c:4
--
Summary: gcc / gdb backtrace problem
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
cc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: kev dot gilbert at cdu dot edu dot au
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24172
--- Additional Comments From kev dot gilbert at cdu dot edu dot au
2005-09-30 01:59 ---
A discussion on another mailing list revealed the page
http://lists.kde.org/?l=kde-devel&m=112537321024777&w=2 where it states that
the bug is in libstdc++ and can be overcome by set
--- Additional Comments From kev dot gilbert at cdu dot edu dot au
2005-09-27 07:28 ---
All three testcases compile & run ok.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19317
--- Additional Comments From kev dot gilbert at cdu dot edu dot au
2005-09-26 23:17 ---
Whilst this bug has been marked as resolved, I am still experiencing the same
problems (with arts-1.4.91 - the version shipped with KDE 35. Beta 1).
My gcc version info : gcc (GCC) 4.1.0
