|
From: Olly B. <ol...@su...> - 2003-10-08 14:41:43
|
On Wed, Oct 08, 2003 at 04:17:32PM +0200, Wim Glassee wrote:
> valgrind --leak-check=yes --leak-resolution=high
What version of valgrind? What version of gcc? What gcc command line
options did you use? What version of glibc?
I can't reproduce your problem with valgrind-20030725 and gcc 2.95.4 or
3.3, with -O, -O2, -O3 or without optimisation. That's using glibc 2.2.5.
I get output from the program and memory leaks reported.
Cheers,
Olly
|