Skip to content

Wireshark: fix fatal warnings for in-tree build#300

Merged
vlvkobal merged 1 commit into
FoxIO-LLC:mainfrom
Boolean263:wireshark-intree-warnings
Jun 19, 2026
Merged

Wireshark: fix fatal warnings for in-tree build#300
vlvkobal merged 1 commit into
FoxIO-LLC:mainfrom
Boolean263:wireshark-intree-warnings

Conversation

@Boolean263

Copy link
Copy Markdown
Contributor

Fix sources of warnings in packet-ja4.c which cause in-tree build to fail, due to upstream Wireshark's use of -Werror. (As tested on Windows build using Visual Studio 2022.)

Remove custom array_length() macro and use <wsutil/array.h> instead, to avoid warnings about macro redefinition.
It's been around long enough now that this plugin can now safely depend on it.

Change loop indexes from int to unsigned to prevent warnings about signed/unsigned mismatches in comparisons.

Fix sources of warnings in `packet-ja4.c` which cause in-tree build to
fail, due to upstream Wireshark's use of `-Werror`. (As tested on
Windows build using Visual Studio 2022.)

Remove custom `array_length()` macro and use `<wsutil/array.h>` instead,
to avoid warnings about macro redefinition.
It's been around long enough now that this plugin can now safely depend
on it.

Change loop indexes from `int` to `unsigned` to prevent warnings about
signed/unsigned mismatches in comparisons.
@vlvkobal

vlvkobal commented Jun 9, 2026

Copy link
Copy Markdown
Member

After this is merged, we won't support Wireshark < 4.4.0 anymore. I don't think that's a real problem, since 4.4.0 was released in August 2024.

@igr001-galactica, what do you think?

If we agree to drop support for older versions, we should update the README files as well.

Alternatively, we can keep support for older versions using preprocessor conditionals.

@vlvkobal vlvkobal merged commit 2a0dc44 into FoxIO-LLC:main Jun 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants