[Snapshot] Format Failure in Busybox Hexdump Output

[bluewavenet]

Sometime in the last few weeks Busybox hexdump started failing to correctly format its output.
Examples -
Failed current version (busybox-1.37.0-r3):

echo -n "0123456789" | hexdump -v -e "\"%08x\""
000000300000003400000038

Working old version (busybox-1.36.1-r2):

echo -n "0123456789" | hexdump -v -e "\"%08x\""
333231303736353400003938

I'm assuming this is a bug unless somebody can enlighten me otherwise...

[efahl]

@bluewavenet

000000300000003400000038

Yeah, that sure looks like a bug to me. Standard GNU hexdump behaves like busybox 1.36.1, looks like 1.37 is somehow truncating the input bytes to the an 8-bit value.

[hnyman]

Likely a manifestation of the bug being discussed in upstream busybox mailing list...

• https://lists.busybox.net/pipermail/busybox/2024-October/date.html

Now they applied a fix, but not yet accepted to 1.37.xxx

• https://git.busybox.net/busybox/commit/?id=87e60dcf0f7ef917b73353d8605188a420bd91f9
• https://lists.busybox.net/pipermail/busybox/2024-December/091044.html

I will still do a PR about cherry-picking that fix to us.

[hnyman]

busybox: Fix hexdump applet with upstream patch

[bluewavenet]

PR now merged. This only effected snapshot.
Thanks to @hnyman @hauke for the fast response!