This is what valgrind reports:
SIR 6 TDI (02) ; RUNTEST 10 TCK; Error: SVF: can not move to RUN/IDLE valgrind: m_mallocfree.c:225 (mk_plain_bszB): Assertion 'bszB != 0' failed. valgrind: This is probably caused by your program erroneously writing past the end of a heap block and corrupting heap metadata. If you fix any invalid writes reported by Memcheck, this assertion failure will probably go away. Please try that before reporting this as a bug. ==15406== at 0x380278E5: report_and_quit (m_libcassert.c:191) ==15406== by 0x38027AB7: vgPlain_assert_fail (m_libcassert.c:265) ==15406== by 0x38032892: unlinkBlock (m_mallocfree.c:225) ==15406== by 0x380343B4: vgPlain_arena_malloc (m_mallocfree.c:1381) ==15406== by 0x38064867: vgPlain_cli_malloc (replacemalloc_core.c:86) ==15406== by 0x38002AF3: vgMemCheck_realloc (mc_malloc_wrappers.c:423) ==15406== by 0x38066F0A: vgPlain_scheduler (scheduler.c:1392) ==15406== by 0x38094154: run_a_thread_NORETURN (syswrap-linux.c:91) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==15406== at 0x4025016: realloc (vg_replace_malloc.c:525) ==15406== by 0x80B6DE8: svf_read_command_from_file (svf.c:721) ==15406== by 0x80B6897: handle_svf_command (svf.c:502) ==15406== by 0x80B0CA8: run_command (command.c:618) ==15406== by 0x80B00A2: script_command_run (command.c:218) ==15406== by 0x80B015C: script_command (command.c:233) ==15406== by 0x8120142: Jim_EvalObj (jim.c:9422) ==15406== by 0x8124DEA: Jim_EvalCoreCommand (jim.c:11579) ==15406== by 0x8120142: Jim_EvalObj (jim.c:9422) ==15406== by 0x81273C9: Jim_CatchCoreCommand (jim.c:12394) ==15406== by 0x8120142: Jim_EvalObj (jim.c:9422) ==15406== by 0x811DB10: Jim_EvalExpression (jim.c:8237) ==15406== by 0x811DC3D: Jim_GetBoolFromExpr (jim.c:8279) ==15406== by 0x81230DD: Jim_IfCoreCommand (jim.c:10692) ==15406== by 0x8120142: Jim_EvalObj (jim.c:9422) ==15406== by 0x8123151: Jim_IfCoreCommand (jim.c:10704) ==15406== by 0x8120142: Jim_EvalObj (jim.c:9422) ==15406== by 0x812321A: Jim_IfCoreCommand (jim.c:10715) ==15406== by 0x8120142: Jim_EvalObj (jim.c:9422) ==15406== by 0x8120880: JimCallProcedure (jim.c:9603) ==15406== by 0x8120178: Jim_EvalObj (jim.c:9426) ==15406== by 0x8124DEA: Jim_EvalCoreCommand (jim.c:11579) ==15406== by 0x8120142: Jim_EvalObj (jim.c:9422) ==15406== by 0x8120880: JimCallProcedure (jim.c:9603) ==15406== by 0x8120178: Jim_EvalObj (jim.c:9426) ==15406== by 0x8120AA4: Jim_Eval_Named (jim.c:9666) ==15406== by 0x80B0E59: command_run_line (command.c:668) ==15406== by 0x80B3CE3: parse_config_file (configuration.c:127) ==15406== by 0x804B223: openocd_main (openocd.c:335) ==15406== by 0x804AB14: main (main.c:42) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
