Ok valgrind have this
Available tools:
memcheck
addrcheck
cachegrind
corecheck
helgrind
massif
lackey
none
So I try
valgrind --tool=memcheck /usr/local/bin/foobillard >& debug2.txt
valgrind --tool=memcheck -v /usr/local/bin/foobillard >& debug3.txt
valgrind --tool=memcheck -v --leak-check=yes /usr/local/bin/foobillard
>& debug4.txt
valgrind --tool=lackey /usr/local/bin/foobillard >& debug5.txt
valgrind --tool=none /usr/local/bin/foobillard
I hate say that, I very sorry about and will try not do again.
foobillard 2.9 works
foobillard 3.0 no,
but foobillard 3.0a works again.
So after Brian fix cvs, everything get to normal, but I tried with
foobillard 3.0, that have a bug, which gives the second problem.
I am very sorry for my mistakes again.
Thanks, now I am going play one little pool for relax :)
On Sun, 2004-04-25 at 16:16, Brian Paul wrote:
> S�rgio Monteiro Basto wrote:
> > On Sat, 2004-04-24 at 15:49, Brian Paul wrote:
> >
> >>When a program segfaults in free(), it's usually because of a memory
> >>error (writing out of bounds, bouble-freeing a block, etc.).
> >>
> >>valgrind will easily find such errors. Once you have it
> >>built/installed, just run 'valgrind myApplication' and see what's
> >>printed out.
> >>
> >>-Brian
> >
> >
> > sorry: wrong txt, now the correct one (I hope)
> >
> > seems that I don't have any ~/.valgrindrc
> >
> > have someone one example of this file ?
>
> I've never needed a .valgrindrc file.
>
> Try valgrind `which foobillard`
>
> -Brian
--
S�rgio M. B.
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg297
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
