public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Oliver Kullmann <O.Kullmann@Swansea.ac.uk>
To: gcc-help@gcc.gnu.org
Subject: Re: Internal compiler error: Segmentation fault
Date: Wed, 23 Jul 2003 16:06:00 -0000	[thread overview]
Message-ID: <20030723152628.GA5354@swan.ac.uk> (raw)
In-Reply-To: <x3oezlz54q.fsf@lifesupport.shutdown.com>

> Oliver Kullmann <O.Kullmann@Swansea.ac.uk> writes:
> 
> > Hi,
> > 
> > I just wanted to finish a quick job, but with my
> > g++ version 3.3 (prelease, Suse 8.2) I got
> > a compiler segmentation fault. So I downloaded
> > the newest version (3.3) and got a similar error:
> > 
> > > make TestDebug
> > g++ -c -I/h/21/GemeinsameBasis/ZentralesArchiv/Hilfsprogramme/C++Bibliothek TestDebug.cpp
> > /home/kullmann/csoliver/GCC/gcc-3.3/include/c++/3.3/iostream:297: internal compiler error: Segmentation
> >    fault
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> 
> Please follow those instructions and report a bug.
>

did so
 
> > make: *** [TestDebug.o] Fehler 1
> > 
> > > g++ -v
> > Reading specs from /home/kullmann/csoliver/GCC/gcc-3.3/lib/gcc-lib/i686-pc-linux-gnu/3.3/specs
> > Configured with: /home/kullmann/csoliver/GCC/gcc-3.3/configure --enable-threads=posix --enable-long-long --prefix=/home/kullmann/csoliver/GCC/gcc-3.3 --with-local-prefix=/home/kullmann/csoliver/GCC/Include_3.3 --enable-languages=c,c++ --disable-nls --enable-shared
> > Thread model: posix
> > gcc version 3.3
> > 
> > I wonder whether someone has seen this before, and knows a quick
> > work around?!
> 
> I'm sorry, there is no hint of what you are trying to do, so I can't
>     figure out an alternative approach, (except perhaps using gcc
>     3.2.2 instead)
> 
> If you would post a short description of what you are trying to do,
>     and short example code that reproduces the problem, it will be
>     much less difficult for someone to help you.

unfortunately, there is nothing to say about the error than the above output:
The error appears erratically over all possible places (that is, in the line

/home/kullmann/csoliver/GCC/gcc-3.3/include/c++/3.3/iostream:297: internal compiler error: Segmentation

most of my own files can appear instead of "iostream", when deleting some stuff in order to localise
the compiler error).

Therefore it doesn't look sensible to me to try to explain the (rather) large project, since the compiler
error doesn't seem to be connected to anything particular in it.

Oliver

  reply	other threads:[~2003-07-23 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 21:46 Oliver Kullmann
2003-07-23 14:46 ` LLeweLLyn Reese
2003-07-23 16:06   ` Oliver Kullmann [this message]
2003-07-29 12:43 ` Andrew Lees
2005-07-20 15:32 internal " J. David Boyd
2007-06-30 12:28 Lee Rhodes
2023-04-08 15:15 Dennis Clarke

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=20030723152628.GA5354@swan.ac.uk \
    --to=o.kullmann@swansea.ac.uk \
    --cc=gcc-help@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).