public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jerome Zago <jerome.zago@insalien.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6707: Segfault when compiling with -ggdb3 (-ggdb2 works)
Date: Wed, 17 Jul 2002 11:16:00 -0000 [thread overview]
Message-ID: <20020717181601.18902.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/6707; it has been noted by GNATS.
From: Jerome Zago <jerome.zago@insalien.org>
To: dr_maux@users.sourceforge.net, gcc-gnats@gcc.gnu.org,
gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/6707: Segfault when compiling with -ggdb3 (-ggdb2 works)
Date: Wed, 17 Jul 2002 18:05:38 +0000
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6707
I cannot reproduce that bug. Besides, http://mindx.dyndns.org/download/GCC-bug-preprocessed doesn't lead anywhere.
$ md5sum preprocessed.ii
7c9c85c3d2d3345f3d11c8c4bb8a99ce preprocessed.ii
$ g++ -v -save-temps -ggdb3 -O2 -fno-exceptions -fno-check-new -c preprocessed.ii -fPIC
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: /usr/src/gcc-3.1/configure --host=i686-pc-linux-gnu --prefix=/usr --enable-threads=posix --enable-languages=c,c++,ada,f77,java,objc
Thread model: posix
gcc version 3.1
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.1/cc1plus -fpreprocessed preprocessed.ii -quiet -dumpbase preprocessed.ii -ggdb3 -O2 -version -fno-exceptions -fno-check-new -fPIC -o preprocessed.s
GNU CPP version 3.1 (cpplib) (i386 Linux/ELF)
GNU C++ version 3.1 (i686-pc-linux-gnu)
compiled by GNU C version 3.1.
as -V -Qy -o preprocessed.o preprocessed.s
GNU assembler version 2.12.1 (i686-pc-linux-gnu) using BFD version 2.12.1
--
PGP Public Key: http://slashdot.org/~Jerome Zago/pubkey/
Fingerprint: 8741 62F1 586D D440 C5CA D1CA CBE5 669A 7EA5 D9F9
next reply other threads:[~2002-07-17 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 11:16 Jerome Zago [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 8:26 DJ Delorie
2002-10-25 3:16 Reichelt
2002-10-24 15:13 bangerth
2002-05-17 12:16 dr_maux
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=20020717181601.18902.qmail@sources.redhat.com \
--to=jerome.zago@insalien.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).