public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ayqazi@yahoo.co.uk
To: gcc-gnats@gcc.gnu.org
Subject: c++/4446: Internal crash using rtti on type 'double[][]' during compilation
Date: Tue, 02 Oct 2001 15:36:00 -0000 [thread overview]
Message-ID: <20011002223420.17612.qmail@sourceware.cygnus.com> (raw)
>Number: 4446
>Category: c++
>Synopsis: Internal crash using rtti on type 'double[][]' during compilation
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Tue Oct 02 15:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: ayqazi@yahoo.co.uk
>Release: gcc-3.0.1 (official)
>Organization:
>Environment:
GNU/Linux (self-compiled)
kernel 2.4.10
glibc-2.1.3
binutils-2.11.90.0.15 (linux release, via www.kernel.org)
bash-2.05
>Description:
Command given:
gcc -c typeinfo_crash_bug.cc -v
Output:
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/specs
Configured with: /home/asfand/src/packages/gcc-3.0.1/gcc-3.0.1/configure --prefix=/usr --enable-version-specific-runtime-libs --enable-languages=c,c++ --without-stabs --without-dwarf2 --disable-win32-registry --disable-nls
Thread model: single
gcc version 3.0.1
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/cc1plus -v -D__GNUC__=3 -D__GNUC_MINOR__=0 -D__GNUC_PATCHLEVEL__=1 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -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__ typeinfo_crash_bug.cc -D__GNUG__=3 -D__GXX_DEPRECATED -D__EXCEPTIONS -D__GXX_ABI_VERSION=100 -quiet -dumpbase typeinfo_crash_bug.cc -version -o /tmp/cc6lBSUO.s
GNU CPP version 3.0.1 (cpplib) (i386 Linux/ELF)
GNU C++ version 3.0.1 (i686-pc-linux-gnu)
compiled by GNU C version 3.0.1.
ignoring nonexistent directory "/usr/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/X11R6/include
/opt/include
/home/asfand/include
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/include/g++
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/include/g++/i686-pc-linux-gnu
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/include/g++/backward
/usr/local/include
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/include
/usr/include
End of search list.
typeinfo_crash_bug.cc: In function `int main()':
typeinfo_crash_bug.cc:6: 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:
Contents of file typeinfo_crash_bug.cc:
#include <iostream>
#include <typeinfo>
int main()
{
std::cout << typeid(double[][]).name() << std::endl;
return 0;
}
>Fix:
Use one or less square bracket pair in the typeid call...
at least then it gives a proper error message! :P
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-10-02 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 15:36 ayqazi [this message]
2001-11-07 23:35 lerdsuwa
2001-11-08 4:15 lerdsuwa
2001-11-09 12:15 lerdsuwa
2001-11-09 12:53 lerdsuwa
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=20011002223420.17612.qmail@sourceware.cygnus.com \
--to=ayqazi@yahoo.co.uk \
--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).