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 B5C333857039; Wed, 16 Sep 2020 23:27:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B5C333857039
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1600298835;
 bh=jshixmzvQimwH3bCCpNhcsIDF3eFNBzpAjiA0OSl6zU=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=LWRymxSnCOJEB6/Vl/Xj0+L70wCHEMo3HXL1df+r9xfij9wMAR0VVcDaJeBYN3+u9
 NsmVevpwQcJVHt4iNbtEFFUgOaO4N4xULSJWzXUTpvYM67Z5uHqMCkfZecikqqhseZ
 TZlcTpBgbsKK4bJmEaDIDfOvxyB/UGdSsKJ3CeFk=
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/95188] analyzer-unsafe-call-within-signal-handler
 shows wrong statement for signal registration event
Date: Wed, 16 Sep 2020 23:27:15 +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: 10.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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: everconfirmed cf_reconfirmed_on bug_status
Message-ID: <bug-95188-4-emHj7KdkIJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95188-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95188-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2020 23:27:15 -0000

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

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2020-09-16
             Status|UNCONFIRMED                 |ASSIGNED

--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to CVS Commits from comment #1)
> The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org=
>:
>=20
> https://gcc.gnu.org/g:b28491dc2d79763ecbff4f0b9f1f3e48a443be1d
>=20
> commit r11-3245-gb28491dc2d79763ecbff4f0b9f1f3e48a443be1d
> Author: David Malcolm <dmalcolm@redhat.com>
> Date:   Tue Aug 18 18:52:17 2020 -0400
>=20
>     analyzer: bulk merger/processing of runs of nodes at CFG join points

[...]

>     The patch fixes a state explosion seen in bzip2.c seen when attempting
>     to reproduce PR analyzer/95188, in a switch statement in a loop for
>     argument parsing.  With this patch, the analyzer successfully
>     consolidates the state after the argument parsing to a single exploded
>     node.

[...]

As noted above, I'm currently not able to reproduce this bug.  My guess is =
that
there was a pre-existing failure to fully explore the program and we previo=
usly
were lucky to explore enough to trigger the bug, but at some point (probably
the reimplementation of state tracking of
r11-2694-g808f4dfeb3a95f50f15e71148e5c1067f90a126d) the bug is now in the
unexplored section.

The above commit from comment #1 will help, but I'm still not able to repro=
duce
the bug.  Marking as ASSIGNED since the state-explosion issue ought to be
fixed, and I can at least reproduce that.=