From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 136A3395B435; Wed, 16 Nov 2022 15:54:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 136A3395B435
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1668614095;
	bh=3HHloPUxOAvIM7HNf40V9H1//sasis9OGAlt4V1U//w=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=y0tv2voaoXfr3kVSHEFRb8z9l5krHI89SblqTr1I5KWZvFeNXy0kzcPDiarmumGkt
	 lavEnhkHKIJlm8SorEiQfruwfiMRRpFpSvjn3vNHl601thuWXxLfieM4UVjhWSYgiU
	 VpdPziIWLrQoltXwqWdViZyr1jXCuXTyfSlQO5WU=
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 15:54:54 +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: dmalcolm at gcc dot gnu.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: <bug-107711-4-A071Iequpy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107711-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to urs from comment #2)
> On Wed, Nov 16, 2022 at 02:41:40PM +0000, dmalcolm at gcc dot gnu.org wro=
te:
> > Unfortunately I can't reproduce the ICE with the attachment.
>=20
> Yes, attachment was created with "-v -save-temps -freport-bug" and with t=
hat
> the crash doesn't show up.

Thanks!

That seems to confirm my suspicion about what's crashing.

I think it's crashing when the analyzer asks the C frontend for the value of
one of these names:
  O_ACCMODE
  O_RDONLY
  O_WRONLY
  SOCK_STREAM
  SOCK_DGRAM
but it's not clear to me how that could fail.

It would be good to know which name it's failing on, and how it's
defined/declared in your headers.

If you're familiar with gdb, would you be able to reproduce the crasher und=
er
gdb, by adding:
  -wrapper gdb,--args
to the crashing gcc invocation, and getting a backtrace at the point of the
crash.

Otherwise, would you be able to try rebuilding gcc with attachment 53911, a=
nd
then use -fdump-analyzer, which with that patch ought to dump which name it=
's
failing on (the dump is written to SOURCEFILE.analyzer.txt).

Sorry about this.=