public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/24994]  New: raised STORAGE_ERROR : stack overflow or erroneous memory access
Date: Wed, 23 Nov 2005 03:10:00 -0000	[thread overview]
Message-ID: <bug-24994-276@http.gcc.gnu.org/bugzilla/> (raw)

../../xgcc -B../../ -c -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmis
sing-prototypes -fno-common -mdisable-indexing     -gnatpg -gnata -I- -I../rts
-
I. -I/xxx/gnu/gcc-3.3/gcc/gcc/ada /xxx/gnu/gcc-3.3/gcc/gcc/ada/make.adb -o
make.
o

raised STORAGE_ERROR : stack overflow or erroneous memory access
make[3]: *** [make.o] Error 1

I've seen this both on hppa2.0w-hpux11.11 and hppa1.1-hp-hpux10.20.

It appears to be a garbage collection problem.


-- 
           Summary: raised STORAGE_ERROR : stack overflow or erroneous
                    memory access
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ada
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
 GCC build triplet: hppa*-*-hpux* (32-bit)
  GCC host triplet: hppa*-*-hpux* (32-bit)
GCC target triplet: hppa*-*-hpux* (32-bit)


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


             reply	other threads:[~2005-11-23  3:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-23  3:10 danglin at gcc dot gnu dot org [this message]
2005-11-23 11:10 ` [Bug ada/24994] " ebotcazou at gcc dot gnu dot org
2005-12-13  2:19 ` danglin at gcc dot gnu dot org
2005-12-13  2:29 ` danglin at gcc dot gnu dot org
2005-12-15 23:43 ` pinskia at gcc dot gnu dot org
2005-12-15 23:45 ` pinskia at gcc dot gnu dot org
2005-12-16  6:50 ` ebotcazou at gcc dot gnu dot org
2005-12-16  7:51 ` laurent at guerby dot net
2005-12-17 12:19 ` christian dot joensson at gmail dot com
2005-12-17 14:54 ` danglin at gcc dot gnu dot org
2005-12-20 21:19 ` laurent at guerby dot net
2006-01-04 16:29 ` law at gcc dot gnu dot org
2006-01-04 16:36 ` law at redhat dot com
2006-01-06  0:12 ` danglin at gcc dot gnu dot org
2006-01-06  1:29 ` danglin at gcc dot gnu dot org
2007-03-27 21:38 ` ebotcazou at gcc dot gnu dot org
2007-03-27 23:49 ` dave at hiauly1 dot hia dot nrc dot ca
2007-03-28 10:46 ` 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=bug-24994-276@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).