Re: [Valgrind-users] porition names length

On 28.10.2015 12:04, Marco Cisternino wrote: > Good morning, > > I'm new on the list and I would like to ask you something about the Valgrind > output. > > My c++ code uses a lot of templates so the name of the functions are usually > huge. > > When Valgrind finds an error, it prints the type

[Valgrind-users] valgrind and gdb

Good morning, I can't use valgrind with gdb. In a terminal I launch my code (real) with valgrind valgrind --vgdb=yes --vgdb-error=0 ./real and valgrind answer me ==23498== (action at startup) vgdb me ... ==23498== ==23498== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==23498==

Re: [Valgrind-users] porition names length

Thank you very much Florian, no problem with 3.11.0 version of Valgrind. It helps me a lot in fixing a wrong memory access. Bests, Marco Da: Florian Krohm Inviato: mercoledì 28 ottobre 2015 13.03 A: Marco Cisternino;

Re: [Valgrind-users] porition names length

I'm sorry for the double mail... Thank you very much for your help Version 3.11.0 completely solved my problem. Bests, Marco Da: Florian Krohm Inviato: mercoledì 28 ottobre 2015 13.03 A: Marco Cisternino;

Re: [Valgrind-users] valgrind and gdb

> gdb ./real > target remote | /usr/local/lib/valgrind/../../bin/vgdb --pid=23498 > continue > After few seconds gdb says > > > Program received signal SIGTRAP, Trace/breakpoint trap. > 0x06018417 in __libc_writev (fd=9, vector=0x6af6710, count=3) at >

[Valgrind-users] Trying to figure out if errors from app linked with IntelMPI are spurious

I have an application with a hard-to-find segfault problem that is compiled against IntelMPI and linked with valgrind MPI wrappers, and I when I try to run it with Valgrind, I get several possibly spurious (?) errors of the following forms: Invalid read of size 8 at 0x5D3D570: free

Re: [Valgrind-users] valgrind and gdb

Hi John, Valgrind 3.11.0 Ubuntu 13.04 Intel i7 -4700HQ (Haswell) gdb version 7.5.91.20130417-cvs-ubuntu I didn't really understand your question, then I don't know how to answer you. Sorry. About gdb commands: when do I have to try them? After the "target remote" one? Thanks, Marco

Re: [Valgrind-users] valgrind and gdb

> Valgrind 3.11.0 > Ubuntu 13.04 > Intel i7 -4700HQ (Haswell) > gdb version 7.5.91.20130417-cvs-ubuntu Thank you. This helps set an explicit context, and reduces misunderstandings. > I didn't really understand your question, then I don't know how to answer > you. Sorry. > About gdb commands:

Re: [Valgrind-users] Trying to figure out if errors from app linked with IntelMPI are spurious

I'm not sure what to make of these instances of "Invalid read error". If I try a simple test program where I feed free() a pointer that is off from a pointer that's been properly malloc'd, I get an "Invalid free() / delete / delete[] / realloc()"