Alexander Kabaev wrote:
> Calling freeenv with the pointerm different from one received from
> getenv seldom is a good idea :)
[...]

Indeed.  Sorry for this yet another freeenv() breakage ; this patch
looks good.

Maxime

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to