[Bug analyzer/95188] State explosion on bzip2-1.0.8/bzip2.c hides -Wanalyzer-unsafe-call-within-signal-handler

[dmalcolm at gcc dot gnu.org]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|analyzer-unsafe-call-within |State explosion on
                   |-signal-handler shows wrong |bzip2-1.0.8/bzip2.c hides
                   |statement for signal        |-Wanalyzer-unsafe-call-with
                   |registration event          |in-signal-handler

--- Comment #14 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Comment #9 noted that the original issue here (the wrong location) was fixed,
but the remaining issues are to do with state explosions.  I tested with
today's trunk, and the state explosions still happen (and, for me mask the
signal warning, unless I pass e.g. --param=analyzer-bb-explosion-factor=50

Updating subject to reflect that (rather than opening a new bug, to keep the
conversation in one place)