arndt at jjj.de
Sun Dec 19 19:17:02 CET 2010
One such is valgrind, use to prefix the binary e.g. like this:
valgrind --leak-check=full --show-reachable=yes ./a.out
This helped me to spot a few memory leaks in the past that
would have most likely gone undetected indefinitely otherwise.
* Paul Leyland <paul at leyland.vispa.com> [Dec 19. 2010 19:12]:
> Obvious question: have you compiled and run under a leak detector? If
> not, please do so. There are any number of them around, particularly
> for the X86 architecture, and most can be found very easily via Google.
> On Sat, 2010-12-18 at 13:59 -0500, Craig Helfgott wrote:
> > The routine does what it is supposed to -- it computes exp(b) to the desired
> > precision. The only thing I need to know is if I've done something in this
> > routine that would cause a memory leak.
> > On Sat, Dec 18, 2010 at 3:45 AM, Torbjorn Granlund <tg at gmplib.org> wrote:
> > > Craig Helfgott <chelfgott at gmail.com> writes:
> > >
> > > Okay, here is my exp subroutine, can you please tell me what I am doing
> > > wrong?
> > >
> > > I'm afraid that's too much code for the time I can spend on this. You
> > > need to make a small example that exhibits the problem, or hope somebody
> > > else is willing to help.
> > >
> > > --
> > > Torbjörn
> > >
> > _______________________________________________
> > gmp-discuss mailing list
> > gmp-discuss at gmplib.org
> > https://gmplib.org/mailman/listinfo/gmp-discuss
> gmp-discuss mailing list
> gmp-discuss at gmplib.org
More information about the gmp-discuss