[cfe-dev] [analyzer][GSoC] Problem Statement: Improving BugReporter with static backward program slicing

[Kristóf Umann via cfe-dev]

Let's hope this works now:

[image: image.png]

On Thu, 4 Apr 2019 at 00:45, Artem Dergachev <noqnoqneo at gmail.com> wrote:

> If i understand correctly (hmm, there seem to be image problems again), in
> this bug report it's about doing trackNullOrUndefValue() over `n` whenever
> we track the uninitialized value back to a load from an array with index
> `n` - i think it easily gets us straight to `a = 3` and it doesn't require
> introducing any new analyses.
>

The problem is, as seen on the image, that it isn't obvious at all from the
report that a == 3.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20190404/d19e719d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 126147 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20190404/d19e719d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 171712 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20190404/d19e719d/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 57345 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20190404/d19e719d/attachment-0002.png>