[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: valgrind on FC2 (undefined symbol: __libc_accept)



Neal Becker wrote:

> Agreed, but valgrind in *very* important, so hopefully libc developers can 
> work together wih valgrind developers to prevent breakage.

If you think it's important, then volunteer your time to check that
valgrind doesn't do anything stupid [*].  For me it's one of a gazillion
of programs which are "important".  I'm not checking whether a change
will break any of them if the change which is made is valid.  Why should
I pick a few programs and treat them special?


[*] Which is, incidently, to a large extend very simple.  If a program
uses symbols with version GLIBC_PRIVATE it is using internal interfaces.
 And guess what?  __libc_accept has this version.

-- 
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]