Hi Sascha, On 20-12-2021 15:24, Sascha Steinbiss wrote:
We have porters for architecture specific support. However, I'm not totally convinced yet it's architecture specific.Maybe. You noted that it seems to work fine on a machine with the same architecture but different specs.
I think you misunderstood me then. We only have one host where we run armhf tests (we do have other arm64 hosts, but we use those for arm64 testing).
Is there anything I can try out for you on our armhf host to help debug the issue? Run the command with more debug options? Grab an output file from somewhere?Hmmm. Since I am pretty unfamiliar with the source and/or any assumptions that are being made in the code, a good start would be to get an idea of where in the code the bus error is triggered. You could try the -v option but I am not sure it would help much.
root@elbrus:/tmp/autopkgtest-lxc.9j0ja_rt/downtmp/build.ssB/real-tree# pktanon -vc /usr/share/doc/pktanon/examples/profiles/profile.xml ./profiles/sample.pcap ./out.pca
----------------------------------------------- pktanon --- profile-based traffic anonymization -----------------------------------------------initializing PktAnon, configuration = /usr/share/doc/pktanon/examples/profiles/profile.xml
parsing configuration file...
unknown element: pktanon-config: 37
unknown element: anonymizations: 102
parsed configuration file.
configuring transformations...
configuring ethernet packet:
mac-source[0]: AnonHashHmacSha1
mac-dest[0]: AnonHashHmacSha1
ethertype[0]: AnonIdentity
configuring arp packet:
hardware-type[0]: AnonIdentity
protocol-type[0]: AnonIdentity
hardware-size[0]: AnonIdentity
protocol-size[0]: AnonIdentity
opcode[0]: AnonIdentity
sender-mac[0]: AnonHashHmacSha1
sender-ip[0]: AnonHashSha1
target-mac[0]: AnonHashHmacSha1
target-ip[0]: AnonHashSha1
configuring ip(v4) packet:
tos[0]: AnonConstOverwrite
identification[0]: AnonIdentity
flags[0]: AnonIdentity
fragment[0]: AnonIdentity
ttl[0]: AnonWhitenoise
protocol[0]: AnonIdentity
src-ip[0]: AnonHashSha1
dest-ip[0]: AnonHashSha1
options[0]: AnonShorten
newlen: 0
configuring ipv6 packet:
traffic-class[0]: AnonIdentity
flow-label[0]: AnonIdentity
next-header[0]: AnonIdentity
hop-limit[0]: AnonWhitenoise
src-ip[0]: AnonHashSha256
dest-ip[0]: AnonHashSha256
configuring tcp packet:
source-port[0]: AnonRandomize
dest-port[0]: AnonRandomize
seq[0]: AnonWhitenoise
ack[0]: AnonWhitenoise
flags[0]: AnonIdentity
window-size[0]: AnonWhitenoise
urgent-pointer[0]: AnonConstOverwrite
options[0]: AnonShorten
newlen: 0
configuring udp packet:
source-port[0]: AnonRandomize
dest-port[0]: AnonRandomize
configuring icmp(v4) packet:
type[0]: AnonIdentity
code[0]: AnonIdentity
rest[0]: AnonIdentity
configuring icmp(v6) packet:
type[0]: AnonIdentity
code[0]: AnonIdentity
rest[0]: AnonIdentity
target-address[0]: AnonHashSha256
configuring payload packet:
payload[0]: AnonShorten
newlen: 0
configured
istream: opened file ./profiles/sample.pcap
ostream: opened output file ./out.pca
initialized
Bus error
(Mind you this was pktanon/unstable build in testing and installed there).
I think a real stack trace would help, by running the tests with valgrind or via gdb. Nothing one would do in a generic test suite :/
I very much not fluent in valgrind and gdb. Please provide the exact commands you'd want me to execute and I'll see if I can get them.
How much customization would be possible in the test run?
I have a shell after the failure, so I can run what I want. I just don't want to change packages before and build them.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
