tiomap-dev team mailing list archive

[Loïc Minier <lool@xxxxxxxx>]

Your valgrind is too old; you want either the natty one (newest), or the
one from the linaro overlay PPA https://launchpad.net/~linaro-
maintainers/+archive/overlay/+packages (which is older).

It would be nice if someone, perhaps Linaro, would provide maverick
backports though.

** Changed in: valgrind (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of TI OMAP
Developers, which is a direct subscriber.
https://bugs.launchpad.net/bugs/691173

Title:
  Valgrind complains on arm v7a

Status in “valgrind” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: valgrind

Valgrind complains on arm v7a; does not handled some instruction:

vincent@vincent-panda:~$ valgrind ls
==1368== Memcheck, a memory error detector
==1368== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==1368== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info
==1368== Command: ls
==1368== 
disInstr(arm): unhandled instruction: 0xDFA068F8
                 cond=13(0xD) 27:20=250(0xFA) 4:4=1 3:0=8(0x8)

vex: priv/guest_arm_toIR.c:4773 (disInstr_ARM_WRK): Assertion `0 == (guest_R15_curr_instr & 3)' failed.
vex storage: T total 0 bytes allocated
vex storage: P total 0 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().
==1368==    at 0x3802D0A0: report_and_quit (m_libcassert.c:191)
==1368==    by 0xE28D000B: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==1368==    at 0x40007E1: ??? (in /lib/ld-2.12.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.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: valgrind 1:3.6.0~svn20100724-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-980.1release7-omap4 2.6.35.3
Uname: Linux 2.6.35-980-omap4 armv7l
Architecture: armel
Date: Thu Dec 16 17:36:17 2010
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: valgrind