public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Chris Cleeland <cleeland@ociweb.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: ada/9587: Storage_Error stack overflow (or erroneous memory access) building gnats from RPM Date: Tue, 13 May 2003 14:06:00 -0000 [thread overview] Message-ID: <20030513140601.17914.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/9587; it has been noted by GNATS. From: Chris Cleeland <cleeland@ociweb.com> To: Dara Hazeghi <dhazeghi@yahoo.com> Cc: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: ada/9587: Storage_Error stack overflow (or erroneous memory access) building gnats from RPM Date: Tue, 13 May 2003 08:54:22 -0500 (CDT) Hi, Dara, On Mon, 12 May 2003, Dara Hazeghi wrote: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- > trail&database=gcc&pr=9587 > > Hello, > > gcc 3.2 (20020903 (3.2-7)) is not an official release of gcc (it is by > RedHat, so if you have questions about it, ask them). If you can try > the latest official version of gcc (3.2.3) or the prerelease (3.3) of > the next version and report on your results here, then we may be able > to do something about it. Thanks. Thanks for the followup. As it turned out, this was NOT a problem with any compiler, but rather a problem with some RAM that got installed in the machine. Removing the RAM solved the problem, as did replacing it. -cj -- Chris Cleeland, cleeland_c @ ociweb.com, http://www.milodesigns.com/~chris Principal Software Engineer, Object Computing, Inc., +1 314 579 0066 Support Me Supporting Cancer Survivors in Ride for the Roses 2002 >>>>>>>>> Donate at http://www.milodesigns.com/donate <<<<<<<<<
next reply other threads:[~2003-05-13 14:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-13 14:06 Chris Cleeland [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 10:34 giovannibajo 2003-05-13 6:30 steven 2003-05-13 0:46 Dara Hazeghi 2003-02-05 17:16 cleeland
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=20030513140601.17914.qmail@sources.redhat.com \ --to=cleeland@ociweb.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).