Wireshark · Wireshark-dev: Re: [Wireshark-dev] Build boot stuck?

[Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx>]

Yes, I was thinking the same.  I should probably do the same for the case below too (for open files).

On Tue, Jul 7, 2020 at 4:53 PM Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:

It might be more useful to simply exit if `cppcheck.sh -l <n>` doesn't match any files. Proposed fix inbound in https://code.wireshark.org/review/c/37773/.

On 7/7/20 7:10 AM, Martin Mathieson via Wireshark-dev wrote:
> Alexis,
>
> Anders change https://code.wireshark.org/review/#/c/37770/ only affects a header file.
> Is it now running cppcheck -l 1, which would scan the whole tree?
>
> Martin
>
> On Tue, Jul 7, 2020 at 3:05 PM Anders Broman via Wireshark-dev <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>> wrote:
>
>     Hi,____
>
>     The latest build seems to take a long time…____
>
>     /Anders____
>
>     ___________________________________________________________________________
>     Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>
>     Archives:    https://www.wireshark.org/lists/wireshark-dev
>     Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>                  mailto:wireshark-dev-request@xxxxxxxxxxxxx <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>