From: Denis Zaitsev <zzz@cd-club.ru>
To: Nix <nix@esperi.demon.co.uk>
Cc: Richard Henderson <rth@redhat.com>, gcc@gcc.gnu.org
Subject: Re: BUG? -fomit-frame-pointer and exceptions or setjmp/longjmp
Date: Thu, 13 Jun 2002 17:15:00 -0000 [thread overview]
Message-ID: <20020614052419.A6289@natasha.zzz.zzz> (raw)
In-Reply-To: <87fzzuc12b.fsf@amaterasu.srvr.nix>; from nix@esperi.demon.co.uk on Mon, Jun 10, 2002 at 09:48:28PM +0100
On Mon, Jun 10, 2002 at 09:48:28PM +0100, Nix wrote:
> ...
> As the trace shows, this crash occurs during unwinding, the presence or
> absence of a catch is irrelevant. I'm rather wondering why we're hitting
> MD_FALLBACK_FRAME_STATE_FOR at all: perhaps there's a problem in FDE
> generation or something.
Exact, uw_update_context_1 calculates bad context->cfa, if it works
for a function with the frame pointer omited. Now I'm looking what
follows...
next prev parent reply other threads:[~2002-06-13 23:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 14:31 Denis Zaitsev
2002-06-02 15:11 ` Richard Henderson
2002-06-02 15:45 ` Denis Zaitsev
2002-06-02 19:46 ` Richard Henderson
2002-06-10 14:17 ` Nix
2002-06-13 17:15 ` Denis Zaitsev [this message]
2002-06-14 12:45 ` Nix
2002-06-14 13:21 ` Andrew Haley
2002-06-14 15:35 ` Nix
2002-06-14 16:19 ` Richard Henderson
2002-06-17 15:46 ` Denis Zaitsev
2002-06-17 17:25 ` Daniel Berlin
2002-07-01 16:10 ` PATCH: " Denis Zaitsev
2002-07-02 3:20 ` Paolo Carlini
2002-07-03 3:50 ` Denis Zaitsev
2002-07-02 19:45 ` Richard Henderson
2002-07-02 20:18 ` Richard Henderson
2002-07-03 2:32 ` Denis Zaitsev
2002-07-03 10:45 ` Denis Zaitsev
2002-07-03 13:26 ` Richard Henderson
2002-07-03 15:43 ` Mark Mitchell
2002-07-03 16:03 ` Denis Zaitsev
2002-07-03 16:16 ` Richard Henderson
2002-07-03 17:05 ` Denis Zaitsev
2002-07-03 17:24 ` Richard Henderson
2002-07-03 21:28 ` Denis Zaitsev
2002-07-03 23:39 ` Richard Henderson
2002-07-03 23:42 ` Denis Zaitsev
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=20020614052419.A6289@natasha.zzz.zzz \
--to=zzz@cd-club.ru \
--cc=gcc@gcc.gnu.org \
--cc=nix@esperi.demon.co.uk \
--cc=rth@redhat.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).