public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lassi Tuura <lat@cern.ch>
To: <gcc-help@gcc.gnu.org>
Subject: No unwind info for __do_global_ctors_aux / _init?
Date: Tue, 09 Mar 2010 11:28:00 -0000	[thread overview]
Message-ID: <7807360E-0CD1-4340-B876-C146ED5091BE@cern.ch> (raw)

Hi,

I maintain a profiling utility which uses libunwind to capture stack traces on x86-64. One of the several problems we ran into is that stack tracing stops at global constructors for dynamically loaded shared libraries. This seems to be because there is no unwind information for _init / __do_global_ctors_aux.

Is there any way to coax GCC to generate .eh_frame information for these functions?

I tried recompiling one library with and without -fasynchronous-unwind-tables on a RHEL5-derived system with GCC 4.3.4 + binutils 2.19.1, but didn't get the extra unwind info. In fact -fasynchronous-unwind-tables didn't make any difference that I could tell.

Regards,
Lassi

             reply	other threads:[~2010-03-09 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 11:28 Lassi Tuura [this message]
2010-03-10 15:52 ` Ian Lance Taylor
2010-03-10 16:19   ` Lassi Tuura
2010-03-10 16:34     ` Ian Lance Taylor

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=7807360E-0CD1-4340-B876-C146ED5091BE@cern.ch \
    --to=lat@cern.ch \
    --cc=gcc-help@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: link
Be 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).