From: Ian Lance Taylor <iant@google.com>
To: vijay nag <vijunag@gmail.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: C++ exceptions
Date: Fri, 22 Nov 2013 19:47:00 -0000 [thread overview]
Message-ID: <CAKOQZ8zwfxWX03m4jbE5TNBCAkUp8s8r5hRKprzUV2GHPJWOBA@mail.gmail.com> (raw)
In-Reply-To: <CAKhyrx9Px6hn6UYcuoaBf6ZkDK+2axiJiMXWMLz3SGZaTSbT+Q@mail.gmail.com>
On Thu, Nov 21, 2013 at 1:20 AM, vijay nag <vijunag@gmail.com> wrote:
>
> I tried creating a small binary to demonstrate the problem that I had
> been facing with my gcc-4.7.2 tool chain and glibc-2.17. The library
> and binaries were created using exact CFLAGS, CXXFLAGS et al.
> Strangely, the problem doesn't manifest in my example program :(. On
> further hacking and debugging libgcc, I found that
> _Unwind_RaiseException() was always "returning" in failure case with
> return code _URC_END_OF_STACK. Does it mean that FDE is missing for
> the function which is suppose to catch the exception ? How do I check
> if an FDE exists for a particular function or not ?
You can use readelf --debug=frames to examine the unwind information
in an executable or object file.
Ian
next prev parent reply other threads:[~2013-11-22 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 12:49 vijay nag
2013-11-20 14:53 ` Marc Glisse
2013-11-20 17:58 ` vijay nag
2013-11-20 17:59 ` Marc Glisse
2013-11-20 18:14 ` Jonathan Wakely
2013-11-21 10:23 ` vijay nag
2013-11-22 19:47 ` Ian Lance Taylor [this message]
2013-11-23 16:40 ` vijay nag
2013-11-23 16:42 ` Jonathan Wakely
2013-11-23 16:54 ` Jonathan Wakely
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=CAKOQZ8zwfxWX03m4jbE5TNBCAkUp8s8r5hRKprzUV2GHPJWOBA@mail.gmail.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=vijunag@gmail.com \
/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).