public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/107711] internal compiler error: Segmentation fault
Date: Wed, 16 Nov 2022 14:41:40 +0000	[thread overview]
Message-ID: <bug-107711-4-6qAF39QHU3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107711-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this bug report.

Unfortunately I can't reproduce the ICE with the attachment.

I have a suspicion that this relates to commits r13-4073-gd8aba860b34203 and/or
r13-4074-g86a90006864840 and that it relates to accessing preprocessor macros
for named constants relating to file descriptors.

To confirm this hypothesis, does the crash go away if you first use -E to run
the preprocessor on its own, and then use -fanalyzer on the preprocessed
source? (with the same other options as before)

(I'd hoped that we could look at the analyzer dump file to confirm this, but
unfortunately the code in question runs before the analyzer's logging code
starts up)

  reply	other threads:[~2022-11-16 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16  0:33 [Bug analyzer/107711] New: " urs at akk dot org
2022-11-16 14:41 ` dmalcolm at gcc dot gnu.org [this message]
2022-11-16 15:26 ` [Bug analyzer/107711] " urs at akk dot org
2022-11-16 15:50 ` dmalcolm at gcc dot gnu.org
2022-11-16 15:54 ` dmalcolm at gcc dot gnu.org
2022-11-16 19:41 ` urs at akk dot org
2022-11-16 19:50 ` urs at akk dot org
2022-11-16 21:15 ` [Bug analyzer/107711] ICE with -fanalyzer with -Wunused-macros since r13-4073-gd8aba860b34203 dmalcolm at gcc dot gnu.org
2022-11-16 22:45 ` [Bug analyzer/107711] [13 Regression] ICE with "-fanalyzer -Wunused-macros" " cvs-commit at gcc dot gnu.org
2022-11-16 23:18 ` dmalcolm at gcc dot gnu.org
2022-11-17  3:07 ` dmalcolm at gcc dot gnu.org
2022-11-17 17:36 ` cvs-commit at gcc dot gnu.org
2022-11-17 17:36 ` dmalcolm at gcc dot gnu.org
2022-11-28 22:24 ` pinskia 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-107711-4-6qAF39QHU3@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).