public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: adrians@aska.com.pl
To: gcc-gnats@gcc.gnu.org
Subject: c++/7975: Segmentation fault
Date: Thu, 19 Sep 2002 01:26:00 -0000	[thread overview]
Message-ID: <20020919081934.9630.qmail@sources.redhat.com> (raw)


>Number:         7975
>Category:       c++
>Synopsis:       Segmentation fault
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 19 01:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     adrians@aska.com.pl
>Release:        gcc-3.2
>Organization:
>Environment:
Environment independend error I think.
>Description:
The command line and output are below, preprocessed file is attached.
The bug is connected with code like this:

extern QArray<something> x;

bash-2.05a$ g++ -c -v -save-temps -I /opt/qt/include -I /opt/kde/include about.cpp
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
Configured with: ../gcc-3.2/configure --prefix=/usr --enable-shared --enable-languages=c,c++ --enable-threads=posix --with-slibdir=/lib --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 3.2
 /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/cpp0 -lang-c++ -D__GNUG__=3 -D__DEPRECATED -D__EXCEPTIONS -v -I /opt/qt/include -I /opt/kde/include -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=0 -D__GXX_ABI_VERSION=102 -D__ELF__ -Dunix -D__gnu_linux__ -Dlinux -D__ELF__ -D__unix__ -D__gnu_linux__ -D__linux__ -D__unix -D__linux -Asystem=posix -D__NO_INLINE__ -D__STDC_HOSTED__=1 -D_GNU_SOURCE -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i686__ -D__tune_pentiumpro__ about.cpp about.ii
GNU CPP version 3.2 (cpplib) (i386 Linux/ELF)
ignoring nonexistent directory "/usr/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /opt/qt/include
 /opt/kde/include
 /usr/include/c++/3.2
 /usr/include/c++/3.2/i686-pc-linux-gnu
 /usr/include/c++/3.2/backward
 /usr/local/include
 /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/include
 /usr/include
End of search list.
 /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/cc1plus -fpreprocessed about.ii -quiet -dumpbase about.cpp -version -o about.s
GNU CPP version 3.2 (cpplib) (i386 Linux/ELF)
GNU C++ version 3.2 (i686-pc-linux-gnu)
        compiled by GNU C version 3.2.
kadu.h:273: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:
Every compilation of this code should do it.
>Fix:
It can be workaround like this:

template QArray<something>;
extern QArray<something> x;

but the compiler should not crash I think ;)
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-09-19  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19  1:26 adrians [this message]
2002-09-28  7:11 lerdsuwa
2003-02-23 20:45 neroden

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=20020919081934.9630.qmail@sources.redhat.com \
    --to=adrians@aska.com.pl \
    --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).