public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/27794] stack explosion
Date: Sat, 15 Jul 2006 20:39:00 -0000 [thread overview]
Message-ID: <20060715203943.16769.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27794-226@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from ebotcazou at gcc dot gnu dot org 2006-07-15 20:39 -------
> Eric, do you have any new information on this problem? I cannot reproduce it.
I'm totally at a loss. I don't have any working debugger on the machine, the
system debugger enters an infinite loop:
azuma% /usr/ccs/bin/gdb32 xgcc
Detected 64-bit executable.
Invoking /usr/ccs/bin/gdb64.
Detected 32-bit executable.
Invoking /usr/ccs/bin/gdb32.
Detected 64-bit executable.
Invoking /usr/ccs/bin/gdb64.
Detected 32-bit executable.
Invoking /usr/ccs/bin/gdb32.
Detected 64-bit executable.
Invoking /usr/ccs/bin/gdb64.
Detected 32-bit executable.
Invoking /usr/ccs/bin/gdb32.
Detected 64-bit executable.
Invoking /usr/ccs/bin/gdb64.
Detected 32-bit executable.
Invoking /usr/ccs/bin/gdb32.
[...]
and building GDB 6.4 doesn't produce anything.
--
ebotcazou at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|0000-00-00 00:00:00 |2006-07-15 20:39:43
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27794
next prev parent reply other threads:[~2006-07-15 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 11:48 [Bug bootstrap/27794] New: " ebotcazou at gcc dot gnu dot org
2006-05-30 18:06 ` [Bug bootstrap/27794] " sje at cup dot hp dot com
2006-06-01 19:14 ` ebotcazou at gcc dot gnu dot org
2006-06-05 18:22 ` sje at cup dot hp dot com
2006-07-13 17:57 ` sje at cup dot hp dot com
2006-07-15 20:39 ` ebotcazou at gcc dot gnu dot org [this message]
2006-07-15 20:40 ` ebotcazou at gcc dot gnu dot org
2006-07-17 17:10 ` sje at cup dot hp dot com
2007-09-17 10:01 ` kari-matti dot pulkkinen at comptel dot com
2008-04-17 6:56 ` cnstar9988 at gmail dot com
2008-04-17 7:18 ` cnstar9988 at gmail dot com
2008-04-18 7:11 ` rwild at gcc dot gnu dot org
2008-05-02 9:15 ` cnstar9988 at gmail dot com
2008-05-02 9:20 ` ebotcazou 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=20060715203943.16769.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).