This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/8743] receiving result from __builtin_return_address() beyond stack top causes segfault
- From: "eddy at opera dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Sep 2005 07:54:04 -0000
- Subject: [Bug middle-end/8743] receiving result from __builtin_return_address() beyond stack top causes segfault
- References: <20021128051601.8743.eddy@opera.no>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From eddy at opera dot com 2005-09-08 07:54 -------
Subject: Re: receiving result from __builtin_return_address() beyond stack top causes segfault
Yes, that's one of the work-arounds I considered: but has an
inconvenient problem - when shared libraries are loading, _start (the
function that calls main) hasn't yet been entered and main hasn't yet
recorded its address. This means we have to not record the call-stack
when our global variable recording main's caller's address is as yet
unset. Indeed, using ccmalloc got me a segfault before main was
entered in exactly this way, since it doesn't (or didn't, back when I
reported this bug - it's about time I had another look at ccmalloc) do
the work-around just described.
Eddy.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8743