public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Ulrich dot Beingesser at t-systems dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29517] Exception handling not thread-safe on AIX5.x with Gnu compilers
Date: Fri, 20 Oct 2006 07:53:00 -0000 [thread overview]
Message-ID: <20061020075333.27211.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29517-10077@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from Ulrich dot Beingesser at t-systems dot com 2006-10-20 07:53 -------
Created an attachment (id=12466)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12466&action=view)
gdb backtrace info
Shows complete sequence how program is build, run, crashes and gdb backtrace on
AIX5.2. On AIX5.3 the same conditions occur, but there we have no gdb available
yet.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29517
next prev parent reply other threads:[~2006-10-20 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 16:44 [Bug c++/29517] New: " Ulrich dot Beingesser at t-systems dot com
2006-10-19 16:45 ` [Bug c++/29517] " Ulrich dot Beingesser at t-systems dot com
2006-10-19 16:51 ` pinskia at gcc dot gnu dot org
2006-10-19 17:02 ` Ulrich dot Beingesser at t-systems dot com
2006-10-19 17:28 ` pinskia at gcc dot gnu dot org
2006-10-20 7:53 ` Ulrich dot Beingesser at t-systems dot com [this message]
2006-10-20 8:08 ` Ulrich dot Beingesser at t-systems dot com
2006-10-20 8:10 ` Ulrich dot Beingesser at t-systems dot com
2006-10-26 18:39 ` Ulrich dot Beingesser at t-systems dot com
2007-01-20 10:37 ` [Bug target/29517] Exception handling not thread-safe on AIX5.x and HP-UX rguenth at gcc dot gnu dot org
2007-07-20 21:22 ` chris at cdnorthamerica dot com
2007-07-24 15:52 ` chris at cdnorthamerica dot com
2007-07-24 16:26 ` dave at hiauly1 dot hia dot nrc dot ca
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=20061020075333.27211.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).