[Bug analyzer/98564] New: valgrind error with -fanalyzer

[Bug analyzer/98564] New: valgrind error with -fanalyzer

[dcb314 at hotmail dot com]

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

            Bug ID: 98564
           Summary: valgrind error with -fanalyzer
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

For this one line of C source code:

void a(void) { int b = calloc(0, 1); }

compiled by recent gcc trunk, built with valgrind, does this:

$ /home/dcb/gcc/results.20210105.valgrind/bin/gcc -fanalyzer -c -w bug687.c
==65008== Conditional jump or move depends on uninitialised value(s)
==65008==    at 0xF7DD7F: ana::exploded_path::feasible_p(ana::logger*,
ana::feas
ibility_problem**, ana::engine*, ana::exploded_graph const*) const
(engine.cc:34
84)
==65008==    by 0x1733AA4: ana::dedupe_winners::add(ana::logger*,
shortest_paths
<ana::eg_traits, ana::exploded_path> const&, ana::exploded_graph const*,
ana::sa
ved_diagnostic*) (diagnostic-manager.cc:465)
==65008==    by 0x1731EF3:
ana::diagnostic_manager::emit_saved_diagnostics(ana::
exploded_graph const&) (diagnostic-manager.cc:616)
==65008==    by 0xF87B77: ana::impl_run_checkers(ana::logger*) (engine.cc:4752)


This bug exists since sometime before 20201206, with git hash 8c23434fdadcf4ca.

[Bug analyzer/98564] valgrind error with -fanalyzer

[dmalcolm at gcc dot gnu.org]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2021-01-06

--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this.  Confirmed; working on a fix.

[Bug analyzer/98564] valgrind error with -fanalyzer

[cvs-commit at gcc dot gnu.org]

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:

https://gcc.gnu.org/g:cffe6dd2ce358c2cb550c9fb3c57cec65eee1c93

commit r11-6512-gcffe6dd2ce358c2cb550c9fb3c57cec65eee1c93
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Wed Jan 6 21:42:56 2021 -0500

    analyzer: fix missing bitmap_clear [PR98564]

    gcc/analyzer/ChangeLog:
            PR analyzer/98564
            * engine.cc (exploded_path::feasible_p): Add missing call to
            bitmap_clear.

    gcc/testsuite/ChangeLog:
            PR analyzer/98564
            * gcc.dg/analyzer/pr98564.c: New test.

[Bug analyzer/98564] valgrind error with -fanalyzer

[dmalcolm at gcc dot gnu.org]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Should be fixed by the above commit