[Valgrind-users] lockup using valgrind on powerpc with eglibc-2.16

[Chris P. <jud...@gm...>]

Hi,

I'm trying to use valgrind on an embedded powerpc system. When I start
a process under valgrind the it seems to lock up. I can connect to the
process using gdb/vgdb and the the following backtrace

  #0  0x0ffbaba8 in _vgr20190ZU_ldZdsoZd1_bcmp (s1V=0x401d000,
s2V=0x401a2e7, n=11) at ../shared/vg_replace_strmem.c:974
  #1  0x0ffbabac in _vgr20190ZU_ldZdsoZd1_bcmp (s1V=<optimized out>,
s2V=<optimized out>, n=<error reading variable: value has been
optimized out>) at ../shared/vg_replace_strmem.c:974

Originally I thought it was a problem with 3.10.0 but I've tried a few
versions and they all seem to have the same type of issue so I think
it's something about our system causing the problem.

We have successfully run valgrind 3.7.0 on an earlier version of our
system using uclibc (after a few patches). I did a quick test with
3.7.0 after convincing configure to allow eglibc-2.16 and got the same
behaviour but given the fact that 3.7.0 doesn't claim to support
glib-2.16 I'm not sure how valid that result is.

Has anyone got any clues as to what I need to do to get valgrind
running on this system?

Thanks,
Chris