Can anyone help to shed the light on mysterious bug in SBCL (found it!)
shamaz.mazum at gmail.com
Thu Apr 17 07:49:17 PDT 2014
2014-04-17 11:42 GMT+04:00 Vasily Postnicov <shamaz.mazum at gmail.com>:
> Thanks for this fix, Matt. If I find more elegant solution, I'll write.
> 2014-04-16 20:37 GMT+04:00 Matthew Dillon <dillon at apollo.backplane.com>:
> I'm looking at how to adjust libthread_xu to clean out the red-zone and
>> thread stack cache(s). Not sure if that will clean everything up
>> there might be (probably are) other allocations that are intended to
>> be persistent hidden in there.
>> In other words, even when we fix the red-zone issue, loading and
>> unloading shared libraries that weren't designed for it causes all
>> sorts of memory leaks and just shouldn't be done by any application.
>> The only shared libraries that should *ever* be unloaded are ones that
>> are designed for load/unload cycling (e.g. things like PAM modules and
>> such, not main-stream libraries).
Oh. I was so simple. In FreeBSD libthr is compiled with this line in the
It works also for libthread_xu.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users