Package: valgrind Version: 1:3.7.0-6 Looks like sgcheck does not like something (ppc):
$ valgrind --tool=exp-sgcheck ./bin/opj_decompress -i ../data/input/nonregression/147af3f1083de4393666b7d99b01b58b_signal_sigsegv_130c531_6155_5136.jp2 -o toto.raw ==5370== exp-sgcheck, a stack and global array overrun detector ==5370== NOTE: This is an Experimental-Class Valgrind Tool ==5370== Copyright (C) 2003-2011, and GNU GPL'd, by OpenWorks Ltd et al. ==5370== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==5370== Command: ./bin/opj_decompress -i ../data/input/nonregression/147af3f1083de4393666b7d99b01b58b_signal_sigsegv_130c531_6155_5136.jp2 -o toto.raw ==5370== exp-sgcheck: sg_main.c:2324 (sg_instrument_IRStmt): the 'impossible' happened. ==5370== at 0x3802ECB8: report_and_quit (m_libcassert.c:210) ==5370== by 0x3802EE8F: vgPlain_assert_fail (m_libcassert.c:284) ==5370== by 0x38028A07: sg_instrument_IRStmt (sg_main.c:2209) ==5370== by 0x38023363: h_instrument (h_main.c:682) ==5370== by 0x380491C7: tool_instrument_then_gdbserver_if_needed (m_translate.c:227) ==5370== by 0x380D553B: LibVEX_Translate (main_main.c:585) ==5370== by 0x3804B95F: vgPlain_translate (m_translate.c:1544) ==5370== by 0x3807B717: vgPlain_scheduler (scheduler.c:901) ==5370== by 0x3808EA8F: run_a_thread_NORETURN (syswrap-linux.c:98) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==5370== at 0xFBC8180: __new_exitfn (cxa_atexit.c:73) ==5370== by 0xFBC83CF: __internal_atexit (cxa_atexit.c:35) ==5370== by 0xFBA8F0F: (below main) (libc-start.c:105) 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. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
