Can anyone help to shed the light on mysterious bug in SBCL (found it!)
Vasily Postnicov
shamaz.mazum at gmail.com
Tue Apr 15 19:59:22 PDT 2014
Thanks! I created a bug report, as it is clear now, that is not SBCL fault.
https://bugs.dragonflybsd.org/issues/2663
I also found that any library, which mmap's some space at fixed range in
its constructor will fail the test. I attached such a library which mimics
the behaviour of libthread_xu.so
2014-04-16 5:31 GMT+04:00 Matthew Dillon <dillon at apollo.backplane.com>:
> Ah ha! I found it. Testing with dynamically loading a library which
> depends on libpthread triggers the problem when libpthread is not
> built into the main program.
>
> For example, if I test with libusb.so.2 with a program compiled without
> -pthread, it triggers the problem. If I test with libusb.so.2 with
> a program compiled with -pthread, it does not trigger the problem.
>
> So the issue here is that libpthread is not built into the main
> program and it needs to be, simple as that. If the main program is
> compiled/linked with -pthread, the problem should go away.
>
> --
>
> In terms of making this work as-is with some sort of fix to rtld-elf...
> that's problematic. A lot of these shared libraries are not designed
> to be unloaded. It would take some time to vet them all.
>
> For now I think the best solution is to adjust the port to compile/link
> SBCL with -pthread.
>
> -Matt
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20140416/e0ec8ec3/attachment-0003.htm>
More information about the Users
mailing list