public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47619] ICE in printf() with -fsplit-stack enabled.
Date: Tue, 08 Feb 2011 18:54:00 -0000	[thread overview]
Message-ID: <bug-47619-4-ToFsesMxCd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47619-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Ian Lance Taylor <ian at airs dot com> 2011-02-08 18:41:53 UTC ---
I just tried glibc 2.12.2 on Fedora 13 and it worked there too.  I don't have a
Fedora 14 system.

This program eats memory and your numbers show it had allocated over 434M when
it crashed for you; do you have a ulimit set?

Otherwise I'm not sure what to suggest without the ability to debug the
program.  I suppose a partial backtrace and some idea of precisely which
instruction was executing at the crash might suggest something (note that the
full backtrace will be huge, and uninteresting).


  parent reply	other threads:[~2011-02-08 18:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 10:17 [Bug target/47619] New: " pluto at agmk dot net
2011-02-06 10:19 ` [Bug target/47619] " pluto at agmk dot net
2011-02-06 11:00 ` pluto at agmk dot net
2011-02-06 19:46 ` ian at airs dot com
2011-02-06 20:27 ` pluto at agmk dot net
2011-02-07  1:59 ` ian at airs dot com
2011-02-07 20:33 ` hjl.tools at gmail dot com
2011-02-08 15:50 ` ian at airs dot com
2011-02-08 15:58 ` hjl.tools at gmail dot com
2011-02-08 18:54 ` ian at airs dot com [this message]
2011-02-08 21:08 ` hjl.tools at gmail dot com
2011-02-08 21:31 ` ian at airs dot com
2011-02-08 21:44 ` hjl.tools at gmail dot com
2011-02-09  1:42 ` ian at airs dot com
2011-02-14 21:40 ` ian at airs dot com
2011-03-09  5:18 ` ian at airs dot com
2011-03-09  7:16 ` hjl.tools at gmail dot com
2011-03-09 14:11 ` ian at airs dot com
2011-03-09 15:11 ` hjl.tools at gmail dot com
2011-04-01  0:30 ` ian at airs dot com

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=bug-47619-4-ToFsesMxCd@http.gcc.gnu.org/bugzilla/ \
    --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).