public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/24025] libstdc++ crashes when out of memory exception thrown
Date: Fri, 02 Dec 2005 17:40:00 -0000	[thread overview]
Message-ID: <20051202174042.26847.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24025-638@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from pcarlini at suse dot de  2005-12-02 17:40 -------
Created an attachment (id=10391)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10391&action=view)
Trivial testcase

Hi. I'm attaching a trivial testcase (*). In fact, I consider this bug pretty
serious! Howard, any chance you can show your patch to Geoff or post it to the
mailing list(s) for a review?

(*) Of course, it reliably fails stand-alone, without the def-out bits, only on
32-bit machines equipped with less than ~ 1G.


-- 


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


       reply	other threads:[~2005-12-02 17:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24025-638@http.gcc.gnu.org/bugzilla/>
2005-12-02 17:40 ` pcarlini at suse dot de [this message]
2005-12-02 17:50 ` pcarlini at suse dot de
2005-12-02 17:51 ` pcarlini at suse dot de
2005-12-02 18:02 ` pcarlini at suse dot de
2005-12-02 18:08 ` pcarlini at suse dot de
2005-12-02 18:13 ` pcarlini at suse dot de
2006-10-23 16:26 ` pcarlini at suse dot de
     [not found] <bug-24025-4@http.gcc.gnu.org/bugzilla/>
2012-02-22 13:10 ` xiaoyuanbo at yeah dot net
2012-11-05 18:21 ` jifl-bugzilla at jifvik dot org
2005-09-22 22:00 [Bug libstdc++/24025] New: " geoffk at gcc dot gnu dot org
2005-09-22 23:05 ` [Bug libstdc++/24025] " pinskia at gcc dot gnu dot org
2005-09-23  9:45 ` pcarlini at suse dot de

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=20051202174042.26847.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).