Re: Buildbot crash - what did I break?

[Pascal Quantin <pascal () wireshark org>]

Hi Chuck

Le jeu. 22 oct. 2020 à 20:06, chuck c <bubbasnmp () gmail com> a écrit :

> https://gitlab.com/wireshark/wireshark/-/issues/16939
> Buildbot crash output: fuzz-2020-10-20-17042.pcap
>
> Git commit
> commit 5b242d62b045e6c85a0119c5271d0b072707c79a
> Author: Chuck Craft <bubbasnmp () gmail com>
> Date:   Tue Sep 8 21:59:02 2020 -0500
>
>     WIN32 logging: connect stdio earlier in main()
>
>
> https://gitlab.com/wireshark/wireshark/-/commit/5b242d62b045e6c85a0119c5271d0b072707c79a
>
> But it seems it might be this commit instead?
>
> https://gitlab.com/wireshark/wireshark/-/commit/0ceb46e1c28d1094a56aefa0ebf7d7c0e00f8849
> proto: add support for FT_BYTES in proto_tree_add_bits

It's not you: you get the reference of the changeset that was fuzzed, which
is not necessarily the one that introduced the issue.

Best regards,
Pascal.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe