public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51722] Options "-g3" or "-ggdb3" or "-g3 -gdwarf-2" and other "-g..level3" - internal compiler error
Date: Tue, 03 Jan 2012 04:39:00 -0000 [thread overview]
Message-ID: <bug-51722-4-iB0d5LstBf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51722-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51722
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hp at gcc dot gnu.org
--- Comment #7 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-01-03 04:39:05 UTC ---
(In reply to comment #6)
> Created attachment 26220 [details]
> For example in Comment 4
Sorry, that file contains a reference to precompiled headers:
#pragma GCC pch_preprocess "./untitled5.gch/c++"
so we'd need "all preprocessed headers to build the PCH" (I'm not sure how to
find those from the above line). On a somewhat closer look, the precompiled
header is found within the Qt-headers, so maybe you just need to rebuild *that*
without precompiled headers to create a debuggable context we can use.
next prev parent reply other threads:[~2012-01-03 4:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 17:31 [Bug c++/51722] New: " ylalym at gmail dot com
2012-01-01 11:11 ` [Bug c++/51722] " paolo.carlini at oracle dot com
2012-01-02 10:16 ` rguenth at gcc dot gnu.org
2012-01-02 15:06 ` ylalym at gmail dot com
2012-01-02 15:16 ` ylalym at gmail dot com
2012-01-02 18:50 ` ylalym at gmail dot com
2012-01-02 18:58 ` ylalym at gmail dot com
2012-01-03 4:39 ` hp at gcc dot gnu.org [this message]
2012-01-03 6:05 ` ylalym at gmail dot com
2012-01-03 6:08 ` ylalym at gmail dot com
2012-01-03 6:17 ` ylalym at gmail dot com
2012-01-03 6:18 ` ylalym at gmail dot com
2012-01-03 9:08 ` [Bug pch/51722] [4.7 Regression] " rguenth at gcc dot gnu.org
2012-01-03 9:55 ` jakub at gcc dot gnu.org
2012-01-03 13:46 ` jakub at gcc dot gnu.org
2012-01-03 13:48 ` jakub at gcc dot gnu.org
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=bug-51722-4-iB0d5LstBf@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).