public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55898] Can't obtain stack trace
Date: Mon, 07 Jan 2013 18:42:00 -0000 [thread overview]
Message-ID: <bug-55898-4-ipRWITgMD1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55898-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55898
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |normal
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-01-07 18:42:21 UTC ---
I bet this is because --enable-sjlj-exceptions turns off the output of the
dwarf2 eh_frame which is used by the debugger to unwind the frames in most
cases if the frame pointer is omitted.
Why are you using SJLJ exceptions anyways? They are much slower when exceptions
don't happen.
next prev parent reply other threads:[~2013-01-07 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 15:02 [Bug c++/55898] New: " net147 at gmail dot com
2013-01-07 16:58 ` [Bug c++/55898] " paolo.carlini at oracle dot com
2013-01-07 18:42 ` pinskia at gcc dot gnu.org [this message]
2013-01-07 18:57 ` vanboxem.ruben at gmail dot com
2013-01-11 10:20 ` net147 at gmail dot com
2013-11-25 21:38 ` ktietz 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=bug-55898-4-ipRWITgMD1@http.gcc.gnu.org/bugzilla/ \
--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: 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).