On Wed, 2013-02-27 at 16:29 +0100, Nils Köhler wrote:
si_code=80; Faulting address: 0x0; sp: 0x62a9d8f8
valgrind INTERNAL ERROR received a signal 11 (SIGSEV)- exiting
I have hundrets of that messages with different SP:adresses
Is it and issue in my programm or in valgrind?
Does anyone
On Wed, 2013-02-27 at 09:58 -0800, John Reiser wrote:
I am on 3.8.1 now and I can not get massif to produce an output
file, neither default name nor specifying it on command line. I
terminate my program by sending TERM signal to valgrind process. That
worked on 3.4.1 (yes, I don't
On Thu, 2013-02-28 at 14:53 -0800, Kyle Mahan wrote:
Hi all, I'm wondering if it's possible for memcheck to show the last
place that some memory was accessible before being leaked. For
example, I would like to see the line numbers for both allocated
here and leaked here in the example below.
Dear Valgrind users,
Am Montag, den 11.02.2013, 12:32 +0100 schrieb Paul Menzel:
first a big thank you to the developers for this great program.
I am using Valgrind 3.8.1-1 from Debian Sid/unstable.
Despite having the debug packages of some packages installed for the
debug symbols and
On Thu, Feb 28, 2013 at 3:28 PM, Philippe Waroquiers
philippe.waroqui...@skynet.be wrote:
IIRC, there was an experimental tool (omega ?)
that was trying to do that.
And here I thought it was a Galaxy Quest reference...
In a Linux (2.6.34) based platform I have a process that does the
functionality of process management by spawning other processes, monitoring
them etc.
For debugging purposes I want to spawn a process using valgrind.. So I fork
and exec with the following parameters to execve
Hi all, I'm wondering if it's possible for memcheck to show the last place
that some memory was accessible before being leaked.
The current implementation of memcheck cannot do this.
Reporting the location of the leak for each leak
would take a major re-think of memcheck. It would be
easier
On 2/28/2013 4:58 PM, John Reiser wrote:
Hi all, I'm wondering if it's possible for memcheck to show the last place
that some memory was accessible before being leaked.
snip
In your example below the difficulty lies in the code that has been elided
by the ellipses If there are any
