-
Notifications
You must be signed in to change notification settings - Fork 290
Closed
Labels
Description
The Debian buildd daemons report "Bus error" in the test suite when building on armhf https://buildd.debian.org/status/fetch.php?pkg=tcpreplay&arch=armhf&ver=4.4.0-1&stamp=1644098099&raw=0:
[tcpprep] Auto/Router mode test: /bin/bash: line 1: 2371998 Bus error ../src/tcpprep --no-arg-comment --dbug=1 -i ./test.pcap -o test.auto_router1 -a router >> test.log 2>&1
make[2]: *** [Makefile:690: auto_router] Error 135
On my local boxes, I can confirm this behaviour.
Bisect led to
af0d523122ebdfb459eec9b9e1dd7dfedddc82cb is the first bad commit
commit af0d523122ebdfb459eec9b9e1dd7dfedddc82cb
Author: Fred Klassen <fklassen@appneta.com>
Date: Thu Jan 27 14:26:32 2022 -0800
Bug #695 remove FORCE_ALIGN
Backtrace, command was:
gdb --args ../src/tcpprep --no-arg-comment --dbug=1 -i ./test.pcap -o test.auto_router1 -a router
Program received signal SIGBUS, Bus error.
0x004050a8 in check_ip6_tree (mode=0, addr=0x448c76) at tree.c:296
296 finder->u.ip6 = *addr;
(gdb) bt
#0 0x004050a8 in check_ip6_tree (mode=0, addr=0x448c76) at tree.c:296
#1 0x0040375c in process_raw_packets (pcap=0x447f10) at tcpprep.c:497
#2 0x004029da in main (argc=9, argv=0xfffef4e4) at tcpprep.c:144
So I'd ask you to re-visit this issue and find a better solution for it.
Reverting that commit doesn't look like a good idea, and also introduces another issue, I haven't checked further:
I: [tcprewrite] L7 fuzzing test: make[2]: *** [Makefile:1062: rewrite_l7fuzzing] Error 1
Reactions are currently unavailable