On Sun, 2008-11-02 at 21:21 -0800, Russ Allbery wrote: > I have some packages that would trigger this because the library uses > generic error handling routines that include functions that can call > exit() or _exit() but which are never called in practice. Ideally, that > dead code would be stripped out of the shared library, but in practice, > this can be more painful to do than is worth it. Hmm, ok. > This sort of check suffers from the problem that there often isn't > anything the Debian maintainer can really do about it. It's not the sort > of thing that warrants making modifications that upstream won't take, > usually (although it can in some situations). Mainly it would be to make the Debian maintainer aware of it so they can contact upstream about it and ask them to fix the situation. In many cases this would mean an ABI change so upstream will likely be unwilling to make the change. > I'm not opposed to adding it, but I think we should probably start with it > marked as experimental, and I'd expect a lot of false positives. Agreed, definitely an info-level complaint if it gets added. -- bye, pabs http://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part