public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/12432] New: backtrace() fails with recursive function on 64-bit
@ 2011-01-23 22:37 loose at astron dot nl
2011-05-14 14:47 ` [Bug libc/12432] " drepper.fsp at gmail dot com
2014-06-27 14:01 ` fweimer at redhat dot com
0 siblings, 2 replies; 3+ messages in thread
From: loose at astron dot nl @ 2011-01-23 22:37 UTC (permalink / raw)
To: glibc-bugs
http://sourceware.org/bugzilla/show_bug.cgi?id=12432
Summary: backtrace() fails with recursive function on 64-bit
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper.fsp@gmail.com
ReportedBy: loose@astron.nl
Created attachment 5207
--> http://sourceware.org/bugzilla/attachment.cgi?id=5207
Test program that demonstrates wrong backtrace on 64-bit
glibc's backtrace() function fails to give a complete backtrace with 64-bit
code when calling a recursive function. A 32-bit executable does produce a
correct backtrace. Using -fno-omit-frame-pointer does not solve the problem for
the 64-bit code.
This problem still exists with current glibc from git. I built glibc from git
at 2011-01-22 and linked the attached program to the freshly built libc. I
tried both static and dynamic linking; both give wrong output.
Output of 32-bit executable:
** 12 **
0 0x80484aa
1 0x8048492
2 0x8048492
3 0x8048492
4 0x8048492
5 0x8048492
6 0x8048492
7 0x8048492
8 0x8048492
9 0x8048492
10 0x804850f
11 0xf75bdc0e
Output of 64-bit executable:
** 2 **
0 0x4005c8
1 0x4005b2
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/12432] backtrace() fails with recursive function on 64-bit
2011-01-23 22:37 [Bug libc/12432] New: backtrace() fails with recursive function on 64-bit loose at astron dot nl
@ 2011-05-14 14:47 ` drepper.fsp at gmail dot com
2014-06-27 14:01 ` fweimer at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: drepper.fsp at gmail dot com @ 2011-05-14 14:47 UTC (permalink / raw)
To: glibc-bugs
http://sourceware.org/bugzilla/show_bug.cgi?id=12432
Ulrich Drepper <drepper.fsp at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #1 from Ulrich Drepper <drepper.fsp at gmail dot com> 2011-05-14 14:46:55 UTC ---
I've checked in a patch.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/12432] backtrace() fails with recursive function on 64-bit
2011-01-23 22:37 [Bug libc/12432] New: backtrace() fails with recursive function on 64-bit loose at astron dot nl
2011-05-14 14:47 ` [Bug libc/12432] " drepper.fsp at gmail dot com
@ 2014-06-27 14:01 ` fweimer at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: fweimer at redhat dot com @ 2014-06-27 14:01 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=12432
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-06-27 14:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-23 22:37 [Bug libc/12432] New: backtrace() fails with recursive function on 64-bit loose at astron dot nl
2011-05-14 14:47 ` [Bug libc/12432] " drepper.fsp at gmail dot com
2014-06-27 14:01 ` fweimer at redhat dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).