/tmp/usr/local/valgrind # ./bin/valgrind -v /sbin/dot1x & /tmp/usr/local/valgrind # ==23190== Memcheck, a memory error detector ==23190== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==23190== Using Valgrind-3.14.0-353a3587bb-20181007X and LibVEX; rerun with -h for copyright info ==23190== Command: /sbin/dot1x ==23190== --23190-- Valgrind options: --23190-- -v --23190-- Contents of /proc/version: --23190-- Linux version 4.4.169-g32247d6-dirty (ngcf@ngcf57) (gcc version 4.9.3 (Buildroot 2015.11.1) ) #1 SMP Mon Mar 25 01:13:59 CST 2019 --23190-- --23190-- Arch and hwcaps: ARM, LittleEndian, ARMv7 --23190-- Page sizes: currently 4096, max supported 4096 --23190-- Valgrind library directory: ./lib/valgrind/ --23190-- Reading syms from /sbin/dot1x --23190-- Reading syms from /lib/ld-2.22.so --23190-- Reading syms from /tmp/usr/local/valgrind/lib/valgrind/memcheck-arm-linux --23190-- object doesn't have a dynamic symbol table --23190-- Scheduler: using generic scheduler lock implementation. --23190-- Reading suppressions file: ./lib/valgrind//default.supp ==23190== embedded gdbserver: reading from /tmp/vsd/0/vgdb-pipe-from-vgdb-to-23190-by-root-on-??? ==23190== embedded gdbserver: writing to /tmp/vsd/0/vgdb-pipe-to-vgdb-from-23190-by-root-on-??? ==23190== embedded gdbserver: shared mem /tmp/vsd/0/vgdb-pipe-shared-mem-vgdb-23190-by-root-on-??? ==23190== ==23190== TO CONTROL THIS PROCESS USING vgdb (which you probably ==23190== don't want to do, unless you know exactly what you're doing, ==23190== or are doing some strange experiment): ==23190== ./lib/valgrind//../../bin/vgdb --pid=23190 ...command... ==23190== ==23190== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==23190== /path/to/gdb /sbin/dot1x ==23190== and then give GDB the following command ==23190== target remote | ./lib/valgrind//../../bin/vgdb --pid=23190 ==23190== --pid is optional if only one valgrind process is running ==23190== ==23190== ==23190== Process terminating with default action of signal 4 (SIGILL): dumping core ==23190== Illegal opcode at address 0x5809DBB8 ==23190== at 0x4000AC0: ??? (in /lib/ld-2.22.so) ==23190== ==23190== HEAP SUMMARY: ==23190== in use at exit: 0 bytes in 0 blocks ==23190== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==23190== ==23190== All heap blocks were freed -- no leaks are possible ==23190== ==23190== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==23190== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) [1]+ Illegal instruction ./bin/valgrind -v /sbin/dot1x /tmp/usr/local/valgrind # ls bin include lib share vgcore.23190 /tmp/usr/local/valgrind # gdb /sbin/dot1x vgcore.23190 GNU gdb (GDB) 8.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-broadcom-linux-gnueabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /sbin/dot1x...done. BFD: warning: /tmp/usr/local/valgrind/vgcore.23190 is truncated: expected core file size >= 2195456, found: 2191360 [New LWP 23190] Core was generated by `'. Program terminated with signal SIGILL, Illegal instruction. #0 0x04000ac0 in ?? () (gdb) x /8x 0x5809DBB8 0x5809dbb8: Cannot access memory at address 0x5809dbb8 (gdb) x /8x 0x4000AC0 0x4000ac0: 0xe59fa094 0xe59f4094 0xe1a0000d 0xeb001061 0x4000ad0: 0xe28f6084 0xe08aa006 0xe79a4004 0xe1a06000 (gdb) quit
Hmm. That feels like "unsupported hardware". What SoC (chip) is this?