|
From: Eric L. <eri...@ab...> - 2005-06-20 16:21:39
|
1: [bzero,memset] so valgring output reachable block because i use bzero instead of memeset? LOL. 2: beside compagny name bashing can you provide insightfull comment? 3: linked library? i dont see where the code snapshot needs any extra linked library to compile beside libc. 4: if you had bad experience in the past with anyone where i work i would appreciate you keep it betwen that person and you.. -elz > -----Original Message----- > From: val...@li...=20 > [mailto:val...@li...] On Behalf=20 > Of Scott Long > Sent: 20 juin 2005 12:09 > To: val...@li... > Subject: Re: [Valgrind-users] An other wierd behavior from valgrind. >=20 > Eric Lauzon wrote: > > Here is an example of code and below is represenation of valgrind=20 > > output which seem buggy. >=20 > I assume from your sig that you are a programmer for "AboveSecurity"=20 > consulting services. Am I to assume that all programmers at=20 > this company are of a similar skill level, e.g. unable to=20 > distinguish between an application and its linked libraries,=20 > and using archaic functions such as bzero()? >=20 > --=20 > Scott Long <sc...@sw...> > Software Engineer > SwiftView, Inc. > (971) 223-2639 >=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_id=3D7477&alloc_id=3D16492&op=3Dclick > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users >=20 |
|
From: Igmar P. <mai...@jd...> - 2005-06-21 08:55:40
|
> 1: [bzero,memset] so valgring output reachable block because > i use bzero instead of memeset? LOL. bzero() is obsolete. > 3: linked library? i dont see where the code snapshot needs any > extra linked library to compile beside libc. Exactly. And if you look close at the error message, you'll se that the memleak is in glibc, either because it is actually leaking, or you don't properly handle those functions. Since getprotobynumber() is using a static buffer, I suggest you switch to getprotobynumber_r(), which is likely to solve your problem, or write a supression. Valgrind is not at fault here. Igmar |