From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E5AC5395A45B; Wed, 16 Nov 2022 15:26:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E5AC5395A45B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1668612402; bh=2ssMuhc/u0i3YuSSbXsxHyhylwIOyMa0P9P+Yy83wRs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aHpBfY2KjWwdhBROxjdiW4F4fy6VAHp+R0EnBmUUnkNXKRFQi/+H+Wo8dtpgBweKC ilyc1qT3BeyDMj6c2V0rbOei6Odvj/cbvnvKEiflZVdYSAMX3vyFoxoTOvm4Cu8lcd 4WpXqdaCC/VZ07KmcozSMpG1JWDYcy2jF38CQgag= From: "urs at akk dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/107711] internal compiler error: Segmentation fault Date: Wed, 16 Nov 2022 15:26:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: analyzer X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: urs at akk dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107711 --- Comment #2 from urs at akk dot org --- On Wed, Nov 16, 2022 at 02:41:40PM +0000, dmalcolm at gcc dot gnu.org wrote: > Unfortunately I can't reproduce the ICE with the attachment. Yes, attachment was created with "-v -save-temps -freport-bug" and with that the crash doesn't show up. Plain source is but it needs a few makros like FreeIfNeeded from which needs autoconf.h ... and so on > I have a suspicion that this relates to commits r13-4073-gd8aba860b34203 = and/or > r13-4074-g86a90006864840 and that it relates to accessing preprocessor ma= cros > for named constants relating to file descriptors. >=20 > 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) gcc-13 -E -I. -I../include -DHAVE_CONFIG_H -DDEBUG -o makecfg.i ./makecfg.c gcc-13 -g -std=3Dc11 -O2 -Wextra -Wpedantic -Wall -Winline -Wshadow -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wbad-function-cast -Wnested-externs -Wcast-align -Wpointer-arith -Waggregate-return -Wcast-qual -Wwrite-strings -Wundef -Wpacked -Wfloat-equ= al -Wunused-macros -Wold-style-definition -Winit-self -Wmissing-include-dirs -Wlogical-op -Wjump-misses-init -Wformat=3D2 -Wshift-overflow=3D2 -Wnull-dereference -Wduplicated-cond -Walloc-zero -Walloca -Wstringop-overflow=3D2 -Wduplicated-branches -Wno-format-nonliteral -Wno-stringop-truncation -Wno-format-truncation -fanalyzer -o makecfg ./makecfg.i works fine (, but then make fails on the next input file, again on the last curly brace in the file): compiling heapsort.o ./heapsort.c:187:1: internal compiler error: Segmentation fault 187 | } | ^ 0x7fd658e6251f ??? ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 0x7fd658e49d8f __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0x7fd658e49e3f __libc_start_main_impl ../csu/libc-start.c:392 niko% wc -l makecfg.c heapsort.c=20 552 makecfg.c 188 heapsort.c HTH, urs=