That's a bit strange. Can you please try with the recently released 3.10.0 version, and see if you still have the problem?
Thanks. J On 09/25/2014 01:41 PM, lchquan wrote: > # /opt/vg/bin/valgrind ls > ==5290== Memcheck, a memory error detector > ==5290== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > ==5290== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info > ==5290== Command: ls > ==5290== > ==5290== > ==5290== Process terminating with default action of signal 4 (SIGILL) > ==5290== Illegal opcode at address 0x3808AE70 > ==5290== at 0x4000E50: _start (in /lib/ld-uClibc-0.9.32.1.so) > valgrind: m_scheduler/scheduler.c:957 (run_thread_for_a_while): Assertion > 'done_this_time >= 0' failed. > ==5290== at 0x38039528: report_and_quit (m_libcassert.c:260) > ==5290== by 0xE08F4003: ??? > sched status: > running_tid=1 > Thread 1: status = VgTs_Runnable > ==5290== at 0x4000E50: _start (in /lib/ld-uClibc-0.9.32.1.so) > > 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. > # cat /proc/cpu > /proc/cpu/ /proc/cpuinfo > # cat /proc/cpuinfo > Processor : ARMv7 Processor rev 1 (v7l) > processor : 0 > BogoMIPS : 1987.37 > processor : 1 > BogoMIPS : 1993.93 > Features : swp half thumb fastmult edsp tls > CPU implementer : 0x41 > CPU architecture: 7 > CPU variant : 0x4 > CPU part : 0xc09 > CPU revision : 1 > Hardware : hi3535 > Revision : 0000 > Serial : 0000000000000000 > # uname -a > Linux (none) 3.4.35_hi3535 #4 SMP Tue Jul 22 11:14:11 CST 2014 armv7l > GNU/Linux > # /opt/vg/bin/valgrind --version > valgrind-3.9.0 > > what's wrong with me? > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Valgrind-users mailing list > Valgrind-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/valgrind-users > ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
