From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb-patches@sourceware.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfa] frame address size incorrect if address size != ptr size
Date: Fri, 06 Aug 2010 11:17:00 -0000 [thread overview]
Message-ID: <201008061117.o76BH8pM015284@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20100806104810.GJ4610@calimero.vinschen.de> (message from Corinna Vinschen on Fri, 6 Aug 2010 12:48:10 +0200)
> Date: Fri, 6 Aug 2010 12:48:10 +0200
> From: Corinna Vinschen <vinschen@redhat.com>
>
> And...
>
> > It would then be interesting to see whether *both* .debug_frame and
> > .eh_frame work on xstormy16 ... you might be able to try the latter
> > by building with -fasynchronous-unwind-tables.
>
> ... .eh_frame sections are never generated for XStormy16. The
> -fasynchronous-unwind-tables option is a no-op.
Is there no C++ exception exception handling on XStormy16? Or did
nobody bother to do the work of switching it away from
setjump/longjump-style exception handling?
next prev parent reply other threads:[~2010-08-06 11:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 14:53 Corinna Vinschen
2010-08-04 11:35 ` Corinna Vinschen
2010-08-04 22:40 ` Jan Kratochvil
2010-08-05 8:06 ` Corinna Vinschen
2010-08-05 10:04 ` Ulrich Weigand
2010-08-05 12:30 ` Corinna Vinschen
2010-08-05 14:08 ` Ulrich Weigand
2010-08-05 14:30 ` Corinna Vinschen
2010-08-05 14:59 ` Ulrich Weigand
2010-08-05 15:30 ` Corinna Vinschen
2010-08-05 16:52 ` Ulrich Weigand
2010-08-06 10:48 ` Corinna Vinschen
2010-08-06 11:17 ` Mark Kettenis [this message]
2010-08-06 12:01 ` Corinna Vinschen
2010-08-06 14:51 ` Ulrich Weigand
2010-08-06 15:57 ` Corinna Vinschen
2010-08-06 16:27 ` Ulrich Weigand
2010-08-06 16:59 ` Corinna Vinschen
2010-08-06 19:03 ` Corinna Vinschen
2010-08-08 14:55 ` Ulrich Weigand
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=201008061117.o76BH8pM015284@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.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).