At Mon, 27 Sep 2004 23:44:11 +0200, Claus Fischer wrote: > If you'd verified this bug you'd have found that the dlclose > has nothing to do with it. > > PLEASE TRY ON A RECENT SARGE:
I'm debian glibc package maintainer using the latest sarge and sid. > cat >main.c <<EOF > #include <dlfcn.h> > int main(int argc, char* argv[]) { dlopen(0,RTLD_LAZY); } > EOF > c++ -o main main.c -ldl > valgrind ./main [EMAIL PROTECTED]:~/debian/glibc/bugs/272219> cat main.c #include <dlfcn.h> int main(int argc, char* argv[]) { dlopen(0,RTLD_LAZY); } [EMAIL PROTECTED]:~/debian/glibc/bugs/272219> c++-3.3 -o main main.c -ldl c++-3.3: ==10396== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward et al. ==10396== Using valgrind-2.2.0, a program supervision framework for x86-linux. ==10396== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al. ==10396== For more details, rerun with: -v ==10396== ==10396== ==10396== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 19 from 1) ==10396== malloc/free: in use at exit: 0 bytes in 0 blocks. ==10396== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. ==10396== For a detailed leak analysis, rerun with: --leak-check=yes ==10396== For counts of detected errors, rerun with: -v Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]