Can anyone help to shed the light on mysterious bug in SBCL (found it!)

[Vasily Postnicov]

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
>> though,
>>     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).
>>
>>                                                 -Matt
>>
>>
>
Oh. I was so simple. In FreeBSD libthr is compiled with this line in the
Makefile:

LDFLAGS+=-Wl,-znodelete

It works also for libthread_xu.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20140417/4b231a41/attachment-0002.html>