Alexander Kabaev wrote:
>
> Hint: Now if only someone could commit it ...
Done, thanks.
Maxime
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
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-cu
Calling freeenv with the pointerm different from one received from
getenv seldom is a good idea :) Indeed, CURRENT panics with the
following stack trace (patch below fixes that):
_mtx_lock_sleep(c08300e4,0,c03644b1,649,c08300e4) at
_mtx_lock_sleep+0x122
_mtx_lock_flags(c08300e4,0,c03644b1,649,c03
