Nicholas Nethercote gmail.com> writes:
>
> On Wed, Sep 23, 2009 at 9:46 PM, Banibrata Dutta
> gmail.com> wrote:
> >
> > I have a x86_64 arch system, running RHEL4.6 x86_64. However, the
application
> > I would like to use Valgrind on, is a 32-bit application (due to some legacy
> > library dep
On Wed, Sep 23, 2009 at 9:46 PM, Banibrata Dutta
wrote:
>
> I have a x86_64 arch system, running RHEL4.6 x86_64. However, the application
> I would like to use Valgrind on, is a 32-bit application (due to some legacy
> library dependencies, which are available 32-bit only).
>
> Should I be using t
How one leak can be "possibly lost", I can't understand this.
If can give a example code!
Thanks,
--
Israel Lins Albuquerque
Desenvolvimento
Polibrás Brasil Software Ltda.
--
Come build with us! The BlackBerry® Develop
On Wed, Sep 23, 2009 at 10:43 AM, Israel Lins Albuquerque
wrote:
> That's works fine for me too, but I can't see the purpose for this...
> I can't see benefices to this option don't stay always on!
I need it off, and in fact I turn even more off, see
https://bugs.kde.org/show_bug.cgi?id=201170
I
works for me. Maybe you need to give --leak-check=full?
$ valgrind --leak-check=full ./a.out
Memcheck, a memory error detector
Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
Using Valgrind-3.6.0.SVN and LibVEX; rerun with -h for copyright info
Command: ./a.out
HEAP SUMMARY
Israel Lins Albuquerque escreveu:
> I can't understand how this work somebody can help me?
> Show me a example!
>
> Regards,
>
>
I understand now see the exemple:
But I fink that option does not make sense to be configurated, this can
always on!!!
#include
#include
int* g = NULL;
int main(
I can't understand how this work somebody can help me?
Show me a example!
Regards,
--
Israel Lins Albuquerque
Desenvolvimento
Polibrás Brasil Software Ltda.
--
Come build with us! The BlackBerry® Developer Conferen
Hi,
I have a x86_64 arch system, running RHEL4.6 x86_64. However, the application
I would like to use Valgrind on, is a 32-bit application (due to some legacy
library dependencies, which are available 32-bit only).
Should I be using the Valgrind v3.5.0 x86_64 version, or the i386 version (x86)