public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gm1981@libero.it
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/10789: segmentation fault during the upgrade from gcc2.95.3 to 3.2.3
Date: Wed, 14 May 2003 17:46:00 -0000	[thread overview]
Message-ID: <20030514173930.16452.qmail@sources.redhat.com> (raw)


>Number:         10789
>Category:       bootstrap
>Synopsis:       segmentation fault during the upgrade from gcc2.95.3 to 3.2.3
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 14 17:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     gcc 3.2.3
>Release:        3.2.3
>Organization:
>Environment:
linux suse i386 kernel 2.4.19-4GB - gcc 2.95.3			
>Description:
I have to upgrade gcc2.95.3 to gcc3.2.3. I exec:
./configure 
no errors
make bootstrap
/home/mauro/Downloads/gcc-3.2.3/gcc/cp/class.c: In function 'build_vbase_offset_vtbl_entries':
/home/mauro/Downloads/gcc-3.2.3/gcc/cp/class.c:7726: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html>for instructions
make[2]: *** [cp/class.o] Error 1
make[2]: Leaving directory '/home/mauro/Documents/objdir/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory '/home/mauro/Documents/objdir/gcc'
make: *** [bootstrap] Error 2
linux:/home/mauro/Documents/objdir #

How can I generate preprocessed sources to upload them
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-05-14 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 17:46 gm1981 [this message]
2003-05-14 20:56 bangerth

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=20030514173930.16452.qmail@sources.redhat.com \
    --to=gm1981@libero.it \
    --cc=gcc-gnats@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).