public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drangon dot mail at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39832] program built by x86_64-pc-mingw32-gcc run crash, maybe for _Unwind_SjLj_Unregister,
Date: Thu, 23 Apr 2009 15:49:00 -0000	[thread overview]
Message-ID: <20090423154917.27586.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39832-15104@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from drangon dot mail at gmail dot com  2009-04-23 15:49 -------
(In reply to comment #1)
> Can you try this again, there were some Exceptions handling issues recently.
> 
I update the newest gcc code from SVN (20090423), and rebuilt the toolchain.
The application built by this new toolchain runs well, no longer crashed.
This bug should bave been fixed. Good Job!


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39832


  parent reply	other threads:[~2009-04-23 15:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21  5:23 [Bug libstdc++/39832] New: " drangon dot mail at gmail dot com
2009-04-22 23:53 ` [Bug middle-end/39832] " pinskia at gcc dot gnu dot org
2009-04-23 15:49 ` drangon dot mail at gmail dot com [this message]
2009-04-23 15:50 ` [Bug middle-end/39832] [4.5 Regression] " pinskia at gcc dot gnu dot org
2009-07-21  7:46 ` drangon dot mail at gmail dot com
2009-07-21  7:48 ` drangon dot mail at gmail dot com
2009-07-25  7:45 ` [Bug middle-end/39832] [4.4/4.5 Regression] program built by x86_64-pc-mingw32-g++ run crash, maybe for _Unwind_SjLj_Unregister or __dyn_tls_dtor drangon dot mail at gmail dot com
2009-07-29 22:33 ` jsm28 at gcc dot gnu dot org
2009-08-30  8:27 ` ktietz at gcc dot gnu dot org
2009-08-30 13:53 ` drangon dot mail at gmail dot com
2009-09-04 12:18 ` fxcoudert at gcc dot gnu dot 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=20090423154917.27586.qmail@sourceware.org \
    --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).