-[ Thu, Sep 01, 2011 at 11:45:37PM +0200, Ludovic Courtès ]---- > Hi Cédric, > > ri...@happyleptic.org skribis: > > > I attached 2 files: > > > > - "guile deadlock.scm > /tmp/log" deadlocks after around 12k lines of > > output for me > > AFAICS the problem does not occur with Guile 2.0. > For 1.8, could you try running Helgrind and see what happens?
Will do. > > - more surprisingly, "guile crash.scm > /dev/log" segfaults with this > > backtrace : > > Well yes, ports still aren???t thread-safe ;-) so this is bound to crash > in unexpected ways. > > With Guile 2.0, it always ends up with: > > --8<---------------cut here---------------start------------->8--- > ERROR: In procedure display: > ERROR: In procedure fport_write: Bad address > --8<---------------cut here---------------end--------------->8--- With guile 2.0.2 it sometimes ends with this or sometime segfaults. See the ticket I opened at savannah here for a backtrace: https://savannah.gnu.org/bugs/?33996
