public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eddy at opera dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/8743] receiving result from __builtin_return_address() beyond stack top causes segfault Date: Thu, 08 Sep 2005 07:54:00 -0000 [thread overview] Message-ID: <20050908075404.30378.qmail@sourceware.org> (raw) In-Reply-To: <20021128051601.8743.eddy@opera.no> ------- 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
next prev parent reply other threads:[~2005-09-08 7:54 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20021128051601.8743.eddy@opera.no> 2003-07-18 23:16 ` [Bug c/8743] " dhazeghi at yahoo dot com 2005-08-20 0:57 ` [Bug middle-end/8743] " pinskia at gcc dot gnu dot org 2005-08-20 2:14 ` pinskia at gcc dot gnu dot org 2005-08-25 11:25 ` eddy at opera dot com 2005-09-08 1:43 ` normbograham at yahoo dot com 2005-09-08 7:54 ` eddy at opera dot com [this message] [not found] <bug-8743-4@http.gcc.gnu.org/bugzilla/> 2012-06-18 19:34 ` gcc at kalvdans dot no-ip.org 2012-06-19 9:18 ` rguenth at gcc dot gnu.org 2015-06-29 15:23 ` msebor at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050908075404.30378.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).