public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "noloader at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/95031] New: GCC 10 Analyzer and fatal error: Terminated signal terminated program cc1plus
Date: Sun, 10 May 2020 06:10:24 +0000	[thread overview]
Message-ID: <bug-95031-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95031

            Bug ID: 95031
           Summary: GCC 10 Analyzer and fatal error: Terminated signal
                    terminated program cc1plus
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: noloader at gmail dot com
  Target Milestone: ---

Created attachment 48496
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48496&action=edit
Preprocessed source file dll.ii

Hi Everyone,

I'm trying out the analyzer on a C++ project. I'm working on Fedora 32 with GCC
10.

  $ gcc --version
  gcc (GCC) 10.0.1 20200430 (Red Hat 10.0.1-0.14)

Here's what I am seeing:

  g++ -fPIC -pthread -pipe -DNDEBUG -g2 -O3 -fanalyzer -c dll.cpp
  g++: fatal error: Terminated signal terminated program cc1plus
  compilation terminated.
  make: *** [GNUmakefile:1693: dll.o] Error 1

It is fairly easy to duplicate with live code. Unfortunately, I am not sure
what is needed for a reproducer based on the error message. It can be
duplicated with live code using:

  $ git clone https://github.com/weidai11/cryptopp.git
  $ cd cryptopp
  $ CXXFLAGS="-DNDEBUG -g2 -O3 -fanalyzer" make dll.o
  ...
  g++: fatal error: Terminated signal terminated program cc1plus
  compilation terminated.

Attached is the output with a -save-temps. If someone would kindly provide
instructions, then I would be happy to troubleshot it further.

The file dll.cpp is a real bastard. It includes a lot of template classes. Its
sole purpose is to instantiate a bunch of template classes so the object file
has concrete objects in it. I would not be surprised if some sort of resource
exhaustion was occurring.

             reply	other threads:[~2020-05-10  6:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-10  6:10 noloader at gmail dot com [this message]
2020-05-11  7:46 ` [Bug analyzer/95031] " marxin at gcc dot gnu.org
2020-05-11  7:54 ` marxin at gcc dot gnu.org
2020-05-11 16:31 ` dmalcolm at gcc dot gnu.org
2020-05-11 17:19 ` noloader at gmail dot com

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-95031-4@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).