[Valgrind-users] Valgrind can't find strcmp in ld.so

Hello. I need some help. I want to start valgrind but get this error. # /mnt/nfs/bin/valgrind/bin/valgrind ls ==933== Memcheck, a memory error detector ==933== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==933== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright

Re: [Valgrind-users] Valgrind doesn't create readable core dumps

Hello I see that gdb can't find general purpose registers. /warning: Couldn't find general-purpose registers in core file.// /Maybe valgrind adds these registers with some wrong offset? On 07/14/2015 04:52 PM, Mikhail Baikov wrote: Architecture is mipsel. OS is Linux. the output of uname

Re: [Valgrind-users] Valgrind doesn't create readable core dumps

Hello. Is there a possibility to disable signals handling by valgrind? The core will be created by the system and that will solve the problem. On 07/02/2015 04:11 PM, Mikhail Baikov wrote: Hello I've got a problem while reading dumps created by valgrind. I've compiled and run this code

[Valgrind-users] Valgrind doesn't create readable core dumps

V0.1 valgrind-3.10.1 -- Sincerely Mikhail Baikov -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus

Re: [Valgrind-users] Problem running even simple programs

On 12/05/2014 09:26 PM, Philippe Waroquiers wrote: On Thu, 2014-12-04 at 16:16 +0300, Mikhail Baikov wrote: And the crash... I'm sorry it's not a segfault. It's a crash. One of the strange things is that inspite of --run-libc-freeres set no in the log appears /bin/sh: symbol '__libc_freeres

Re: [Valgrind-users] Problem running even simple programs

On 12/04/2014 12:44 AM, Philippe Waroquiers wrote: Then I might have missed something in the mail exchanges. Your initial mail said that the bug is valgrind fails to find problems even in simple applications. The example shown was with /bin/true. This was reporting 'invalid read errors'

Re: [Valgrind-users] Problem running even simple programs

On Thu, 2014-11-27 at 23:06 +0300, Mikhail Baikov wrote: ==1654== Invalid read of size 4 ==1654==at 0x489B248: __uClibc_main (in /lib/libuClibc-0.9.32.1.so) ==1654== Address 0xbdd74b44 is on thread 1's stack ==1654== 20 bytes below stack pointer ==1654== I also have # valgrind -v

[Valgrind-users] Problem running even simple programs

Hello I built valgrind 3.10.1 for arm platform (on amd64 host system) and got a problem. Memcheck fails finding problems even in /bin/true # valgrind /bin/true ==1654== Memcheck, a memory error detector ==1654== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==1654== Using