Porting sbcl to DragonFly
Markus Pfeiffer
markus.pfeiffer at morphism.de
Wed Apr 3 07:14:17 PDT 2013
Hi Vasily,
I tried myself porting sbcl to dragonfly, and succeeded insofar as I removed
some kernel panics caused by sbcl.
I cannot though reproduce your problem on my machine right now, can you please
advise me about what version of dragonfly's world/kernel you are using and
which steps exactly i have to take to reproducethe problem?
Looking at threading problems in gdb is usually less than useful.
Cheers,
Markus
On Wed, Apr 03, 2013 at 09:22:09AM +0400, vasily postnicov wrote:
> > I am still concerned about sb-concurrency's symbol-value-in-thread.3 test .
> It always causes sbcl to crash and always in different fashion (sometimes it
> just prints "Illegal instruction" and crashes, sometimes sbcl debugger is
> invoked with "The integrity of this image is possibly compromised" message and
> sometimes there are "[diagnostic] cache_lock: blocked on 0xffffffe00653eac8
> sbcl.core" kernel messages)
>
> Cannot fix it. Still no luck. So I put sbcl binary (for x86-64), lisp file,
> which can cause a crash, and 2 cores of crashed sbcl into archive and hope,
> that someone can help me:
>
> shamazmazum.users.sourceforge.net/sbcl-bin.tar.bz2 (23 M)
>
> The bug has more probability to reproduce, when system is under load (I used
> 'make buildworld'). On idle system this test often completes without any error.
>
> Backtrace usually looks like:
> (gdb) bt
> #0 0x000000080085f864 in _umtx_wakeup_err () from /usr/lib/libpthread.so.0
> Cannot access memory at address 0x80ebcff08
>
> And thread info usually looks like:
> (gdb) info thread
> Id Target Id Frame
> 6 process 765 0x0000000800859dc8 in ?? () from /usr/lib/
> libpthread.so.0
> 5 process 711 0x000000080085f864 in _umtx_wakeup_err ()from /
> usr/lib/libpthread.so.0
> 4 process 705 0x0000000020100019 in ?? ()
> 3 process 1 0x0000001002c458fb in ?? ()
> * 2 process 724 0x000000080085f864 in _umtx_wakeup_err() from /
> usr/lib/libpthread.so.0
>
> Again, sources can be found here:
> https://github.com/shamazmazum/sbcl-dragonfly
>
> in 'dragonfly' branch.
>
> Still no response from sbcl-devel, so you are my only hope ;)
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20130403/1b4fa670/attachment-0002.bin>
More information about the Users
mailing list