* Vesselin Peev:

> I'm thinking of submitting a wish about better handling,

You could reuse this bug report (downgrade it to wishlist, reassign if
necessary).

> if possible with the mudflap architecture, of internal data
> allocated by libc. Proper handling should of course include no
> "unaccessed registered object" warnings. Barring that, I'd request a
> mudflap option to suppress those warnings. What would you advise me?

Mudflap needs some GNU libc interface to do this. __libc_freeres looks
very internal.  It's not documented, either.  I believe it can go away
in the next release.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to