|
From: Eric L. <eri...@ab...> - 2005-06-17 21:59:46
|
Yhea sorry
someone replied=20
> -----Original Message-----
> From: Nicholas Nethercote [mailto:nj...@cs...]=20
> Sent: 17 juin 2005 16:36
> To: Eric Lauzon
> Cc: val...@li...
> Subject: [SPAM] Re: [Valgrind-users] Valgrind memory cleanup,problems
> Importance: Low
>=20
> It seems that way, but it's not the case. Valgrind is=20
> calling __libc_freeres, a glibc function that frees up memory=20
> at the end of a program. So the bug is in glibc, or possibly=20
> the program being checked.
> If you run with --run-libc-freeres=3Dno the warnings should go=20
> away, although that might make leak checking less accurate/useful.
>=20
> [Nb: the "_vgw(float, long double,...)..." is a minor bug in=20
> the stack trace formation -- it should say "_vgw_freeres). =20
> It's not present in 3.0, but I don't know what the change=20
> that fixed it was.]
>=20
> N
so --run-libc-freeres=3Dno fix the core-dump problem. But i still have=20
wierd libc leakage [reported from valgrind]
glibc version is :
GNU C Library stable release version 2.3.4, by Roland McGrath et al.
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.3.4.
Compiled on a Linux 2.4.29 system on 2005-01-28.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
linuxthreads-0.10 by Xavier Leroy
BIND-8.2.3-T5B
libthread_db work sponsored by Alpha Processor Inc
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
valgrind is : 2.4.0 stable.
current kernel is : 2.6.11-7
-elz
=20
> -----Original Message-----
> From: val...@li...=20
> [mailto:val...@li...] On Behalf=20
> Of Julian Seward
> Sent: 17 juin 2005 16:46
> To: val...@li...
> Subject: Re: [Valgrind-users] Valgrind memory cleanup,problems
>=20
>=20
> What version of valgrind is this? What version of glibc?
>=20
> J
>=20
> On Friday 17 June 2005 20:51, Eric Lauzon wrote:
> > =3D=3D20806=3D=3D
> > =3D=3D20806=3D=3D Invalid read of size 4
> > =3D=3D20806=3D=3D at 0x1BA7D0EC: free_derivation (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA403B2: tdestroy_recurse (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA403D5: tdestroy_recurse (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA403D5: tdestroy_recurse (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA40256: tdestroy (in /lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA7D074: free_mem (in /lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA7D7D4: __libc_freeres (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1B8FC817: _vgw(float, long =
double,...)(...)(long
> > double,...)(short) (vg_intercept.c:55) =3D=3D20806=3D=3D by=20
> 0x1B9B3585: exit (in
> > /lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x804A78B: CleanExit (barnyard.c:566)
> > =3D=3D20806=3D=3D by 0x1BAB6C84: __pthread_sighandler (in
> > /lib/libpthread-0.10.so) =3D=3D20806=3D=3D by 0x1B9B0DB7: (within
> > /lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D Address 0xC is not stack'd, malloc'd or=20
> (recently) free'd=20
> > =3D=3D20806=3D=3D =3D=3D20806=3D=3D Process terminating with default =
action=20
> of signal=20
> > 11 (SIGSEGV):
> > dumping core =3D=3D20806=3D=3D Access not within mapped region at=20
> address 0xC
> > =3D=3D20806=3D=3D at 0x1BA7D0EC: free_derivation (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA403B2: tdestroy_recurse (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA403D5: tdestroy_recurse (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA403D5: tdestroy_recurse (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA40256: tdestroy (in /lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA7D074: free_mem (in /lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1BA7D7D4: __libc_freeres (in =
/lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x1B8FC817: _vgw(float, long =
double,...)(...)(long
> > double,...)(short) (vg_intercept.c:55) =3D=3D20806=3D=3D by=20
> 0x1B9B3585: exit (in
> > /lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D by 0x804A78B: CleanExit (barnyard.c:566)
> > =3D=3D20806=3D=3D by 0x1BAB6C84: __pthread_sighandler (in
> > /lib/libpthread-0.10.so) =3D=3D20806=3D=3D by 0x1B9B0DB7: (within
> > /lib/libc-2.3.4.so)
> > =3D=3D20806=3D=3D
> > =3D=3D20806=3D=3D ERROR SUMMARY: 497 errors from 3 contexts =
(suppressed: 41=20
> > from 1) =3D=3D20806=3D=3D malloc/free: in use at exit: 17798 bytes=20
> in 182 blocks.
> > =3D=3D20806=3D=3D malloc/free: 49680 allocs, 49498 frees, 28959643=20
> bytes allocated.
> > =3D=3D20806=3D=3D For counts of detected errors, rerun with: -v =
=3D=3D20806=3D=3D=20
> > searching for pointers to 182 not-freed blocks.
> > =3D=3D20806=3D=3D checked 1141308 bytes.
> > =3D=3D20806=3D=3D
> >
> > All those bugs seem to come from valgrind ..unfortunatly
> >
> > Eric Lauzon
> > [Recherche & D=E9veloppement]
> > Above S=E9curit=E9 / Above Security
> > T=E9l : (450) 430-8166
> > Fax : (450) 430-1858
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration=20
> Strategies=20
> > from IBM. Find simple to follow Roadmaps, straightforward articles,=20
> > informative Webcasts and more! Get everything you need to get up to=20
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3DClick
> > _______________________________________________
> > Valgrind-users mailing list
> > Val...@li...
> > https://lists.sourceforge.net/lists/listinfo/valgrind-users
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration=20
> Strategies from IBM. Find simple to follow Roadmaps,=20
> straightforward articles, informative Webcasts and more! Get=20
> everything you need to get up to speed, fast.=20
> http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dick
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>=20
|