Bug 128042

Summary:	gdb cannot find top of stack
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Andreas Kleen <ak>
Component:	Development	Assignee:	Andreas Schwab <schwab>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	RC 4
Target Milestone:	---
Hardware:	x86-64
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Andreas Kleen 2005-10-13 09:29:27 UTC

Just had a crash in kmail that led kcrash to find the backtrace
and it needed several minutes of CPU time. debuginfo for kmail
was installed

Reason was I think that it backtracked over the top of the stack:

e.g.

#30 0x00002aaaac2305aa in __libc_start_main () from /lib64/tls/libc.so.6
#31 0x00000000004026da in _start () at start.S:113
#32 0x00007fffffe20de8 in ?? ()
#33 0x00002aaaaabc19c0 in rtld_errno () from /lib64/ld-linux-x86-64.so.2
#34 0x0000000000000001 in ?? ()
... <long time>...
#1634 0x0000000000000000 in ?? ()
#1635 0x0000000000000000 in ?? ()

Shouldn't it notice _start somehow and stop there?

Comment 1 Andreas Schwab 2005-10-13 09:43:04 UTC

Do you have glibc-debuginfo installed?

Comment 2 Andreas Kleen 2005-10-13 09:47:23 UTC

No

Comment 3 Andreas Schwab 2005-10-13 09:49:31 UTC

Then try again with glibc-debuginfo installed.

Comment 4 Andreas Kleen 2005-10-13 09:52:44 UTC

Erm, but - is it ok to let kcrash hog the CPU for minutes just because
that package is not installed? Crashing in KDE is not exactly a very
rare event, at least if you use kmail ;-)

Comment 5 Andreas Kleen 2005-11-15 15:01:53 UTC

With debuginfo it doesn't spin that long, but imho the spinning with debuginfo
is still a bug that needs to be addressed (because the default state is having
no debuginfo)

Comment 6 Andreas Schwab 2005-11-29 16:03:51 UTC

Please try out latest gdb.

Comment 7 Andreas Kleen 2007-02-15 13:33:14 UTC

No time to reproduce anymore