Das ursächliche Problem ist die miese Qualtität der Signale am Bus.
pi@raspberrypi /usr/bin $ valgrind --leak-check=full --show-reachable=yes ./ebusd/ebusd ==8071== Memcheck, a memory error detector ==8071== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==8071== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==8071== Command: ./ebusd/ebusd ==8071== ==8071== ==8071== HEAP SUMMARY: ==8071== in use at exit: 360 bytes in 1 blocks ==8071== total heap usage: 11 allocs, 10 frees, 10,498 bytes allocated ==8071== ==8071== 360 bytes in 1 blocks are still reachable in loss record 1 of 1 ==8071== at 0x4835978: malloc (vg_replace_malloc.c:263) ==8071== by 0x48B6DAF: __fopen_internal (iofopen.c:76) ==8071== by 0x1023F: log_open (log.c:88) ==8071== by 0x949B: main (ebusd.c:696) ==8071== ==8071== LEAK SUMMARY: ==8071== definitely lost: 0 bytes in 0 blocks ==8071== indirectly lost: 0 bytes in 0 blocks ==8071== possibly lost: 0 bytes in 0 blocks ==8071== still reachable: 360 bytes in 1 blocks ==8071== suppressed: 0 bytes in 0 blocks ==8071== ==8071== For counts of detected and suppressed errors, rerun with: -v ==8071== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 6) pi@raspberrypi /usr/bin $ ==8076== ==8076== HEAP SUMMARY: ==8076== in use at exit: 0 bytes in 0 blocks ==8076== total heap usage: 15 allocs, 15 frees, 19,132 bytes allocated ==8076== ==8076== All heap blocks were freed -- no leaks are possible ==8076== ==8076== For counts of detected and suppressed errors, rerun with: -v ==8076== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 6) d/ebusdd --leak-check=full --show-reachable=yes ./ebusd ==8078== Memcheck, a memory error detector ==8078== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==8078== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==8078== Command: ./ebusd/ebusd ==8078== ==8078== ==8078== HEAP SUMMARY: ==8078== in use at exit: 360 bytes in 1 blocks ==8078== total heap usage: 11 allocs, 10 frees, 10,498 bytes allocated ==8078== ==8078== 360 bytes in 1 blocks are still reachable in loss record 1 of 1 ==8078== at 0x4835978: malloc (vg_replace_malloc.c:263) ==8078== by 0x48B6DAF: __fopen_internal (iofopen.c:76) ==8078== by 0x1023F: log_open (log.c:88) ==8078== by 0x949B: main (ebusd.c:696) ==8078== ==8078== LEAK SUMMARY: ==8078== definitely lost: 0 bytes in 0 blocks ==8078== indirectly lost: 0 bytes in 0 blocks ==8078== possibly lost: 0 bytes in 0 blocks ==8078== still reachable: 360 bytes in 1 blocks ==8078== suppressed: 0 bytes in 0 blocks ==8078== ==8078== For counts of detected and suppressed errors, rerun with: -v ==8078== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 6) pi@raspberrypi /usr/bin $ ==8082== ==8082== HEAP SUMMARY: ==8082== in use at exit: 0 bytes in 0 blocks ==8082== total heap usage: 15 allocs, 15 frees, 19,132 bytes allocated ==8082== ==8082== All heap blocks were freed -- no leaks are possible ==8082== ==8082== For counts of detected and suppressed errors, rerun with: -v ==8082== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 6) d/ebusdd --leak-check=full --show-reachable=yes ./ebusd ==8084== Memcheck, a memory error detector ==8084== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==8084== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==8084== Command: ./ebusd/ebusd ==8084== ==8084== ==8084== HEAP SUMMARY: ==8084== in use at exit: 360 bytes in 1 blocks ==8084== total heap usage: 11 allocs, 10 frees, 10,498 bytes allocated ==8084== ==8084== 360 bytes in 1 blocks are still reachable in loss record 1 of 1 ==8084== at 0x4835978: malloc (vg_replace_malloc.c:263) ==8084== by 0x48B6DAF: __fopen_internal (iofopen.c:76) ==8084== by 0x1023F: log_open (log.c:88) ==8084== by 0x949B: main (ebusd.c:696) ==8084== ==8084== LEAK SUMMARY: ==8084== definitely lost: 0 bytes in 0 blocks ==8084== indirectly lost: 0 bytes in 0 blocks ==8084== possibly lost: 0 bytes in 0 blocks ==8084== still reachable: 360 bytes in 1 blocks ==8084== suppressed: 0 bytes in 0 blocks ==8084== ==8084== For counts of detected and suppressed errors, rerun with: -v ==8084== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 6) pi@raspberrypi /usr/bin $ ==8088== ==8088== HEAP SUMMARY: ==8088== in use at exit: 0 bytes in 0 blocks ==8088== total heap usage: 15 allocs, 15 frees, 19,132 bytes allocated ==8088== ==8088== All heap blocks were freed -- no leaks are possible ==8088== ==8088== For counts of detected and suppressed errors, rerun with: -v ==8088== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 6)
pi@raspberrypi /usr/bin/ebusd $ sudo valgrind --leak-check=full --show-reachable=yes ./ebusd
==8716== Memcheck, a memory error detector
==8716== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==8716== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==8716== Command: ./ebusd
==8716==
2014-02-10 22:47:47.878 [EBH] 10 50 b5 05 07 2b 00 01 00 00 00 00 24 00 00 00 00
disInstr(arm): unhandled instruction: 0xF1010200
cond=15(0xF) 27:20=16(0x10) 4:4=0 3:0=0(0x0)
==8716== valgrind: Unrecognised instruction at address 0x4843588.
==8716== at 0x4843588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==8716== Your program just tried to execute an instruction that Valgrind
==8716== did not recognise. There are two possible reasons for this.
==8716== 1. Your program has a bug and erroneously jumped to a non-code
==8716== location. If you are running Memcheck and you just saw a
==8716== warning about a bad jump, it's probably your program's fault.
==8716== 2. The instruction is legitimate but Valgrind doesn't handle it,
==8716== i.e. it's Valgrind's fault. If you think this is the case or
==8716== you are not sure, please let us know and we'll try to fix it.
==8716== Either way, Valgrind will now raise a SIGILL signal which will
==8716== probably kill your program.
==8716==
==8716== Process terminating with default action of signal 4 (SIGILL)
==8716== Illegal opcode at address 0x4843588
==8716== at 0x4843588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==8716==
==8716== HEAP SUMMARY:
==8716== in use at exit: 428,008 bytes in 547 blocks
==8716== total heap usage: 1,133 allocs, 586 frees, 57,778,111 bytes allocated
==8716==
==8716== 272 bytes in 1 blocks are still reachable in loss record 1 of 4
==8716== at 0x4835978: malloc (vg_replace_malloc.c:263)
==8716== by 0xA7E7: msg_queue_init (utils.c:53)
==8716== by 0x951F: main (ebusd.c:738)
==8716==
==8716== 1,104 bytes in 1 blocks are still reachable in loss record 2 of 4
==8716== at 0x4835A7C: realloc (vg_replace_malloc.c:632)
==8716== by 0xE023: eb_cmd_fill (ebus-cmd.c:880)
==8716== by 0xE1B3: eb_cmd_file_read (ebus-cmd.c:936)
==8716== by 0xE397: eb_cmd_dir_read (ebus-cmd.c:984)
==8716== by 0x94B3: main (ebusd.c:706)
==8716==
==8716== 211,072 bytes in 1 blocks are still reachable in loss record 3 of 4
==8716== at 0x4835A7C: realloc (vg_replace_malloc.c:632)
==8716== by 0xDB1F: eb_cmd_fill (ebus-cmd.c:780)
==8716== by 0xE1B3: eb_cmd_file_read (ebus-cmd.c:936)
==8716== by 0xE397: eb_cmd_dir_read (ebus-cmd.c:984)
==8716== by 0x94B3: main (ebusd.c:706)
==8716==
==8716== 215,560 bytes in 544 blocks are still reachable in loss record 4 of 4
==8716== at 0x4835978: malloc (vg_replace_malloc.c:263)
==8716== by 0xDD4B: eb_cmd_fill (ebus-cmd.c:835)
==8716== by 0xE1B3: eb_cmd_file_read (ebus-cmd.c:936)
==8716== by 0xE397: eb_cmd_dir_read (ebus-cmd.c:984)
==8716== by 0x94B3: main (ebusd.c:706)
==8716==
==8716== LEAK SUMMARY:
==8716== definitely lost: 0 bytes in 0 blocks
==8716== indirectly lost: 0 bytes in 0 blocks
==8716== possibly lost: 0 bytes in 0 blocks
==8716== still reachable: 428,008 bytes in 547 blocks
==8716== suppressed: 0 bytes in 0 blocks
==8716==
==8716== For counts of detected and suppressed errors, rerun with: -v
==8716== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 6)
pi@raspberrypi /usr/bin/ebusd $
Kommentar