To even more increase strangeness I ran the test script on a notebook with the same Ubuntu version (8.10) and I was unable to reproduce the faulty behavior:
anco...@bitch:~$ ./testBackslashHex.sh Executing backslash '\' test 'echo'... :) stable |-----------------------------------------------------------------------------| Executing backslash '\' test 'hexdump'... :) stable |-----------------------------------------------------------------------------| Executing backslash '\' test 'hexdump -x'... :) stable |-----------------------------------------------------------------------------| Executing backslash '\' test 'hexdump -x -s 1'... :) stable |-----------------------------------------------------------------------------| Executing backslash '\' test 'sed ... | iconv ... | hexdump -x -s 2'... :) stable |-----------------------------------------------------------------------------| Executing backslash '\' test 'xxd'... :) stable |-----------------------------------------------------------------------------| Executing backslash '\' test 'od'... :) stable So to clarify the hardware environments this bug seems to be related with here is a small list of tested machines where the faulty behavior can be seen by running the provided test script: - Intel Pentium 4 with HyperThreading enabled (2 logical CPUs) @ Debian 4 - Dual Intel Xeon Quad-Core (8 logical CPUs) @ Debian 4 - Intel Core 2 Duo (2 logical CPUs) @ Ubuntu 8.10 - AMD Athlon 64 X2 (2 logical CPUs) @ Ubuntu 8.10 And here is a list where I was unable to raise any errors: - Intel Pentium M (1 logical CPU) @ Ubuntu 8.10 All Ubuntu 8.10 machines have the latest patches applied. -- hexdump :: unexpected error when input ends with backslash https://bugs.launchpad.net/bugs/342433 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
