-[ Sun, Sep 04, 2011 at 12:18:15PM +0200, Andy Wingo ]
> > Actually 1.8 has a serious problem when it comes to multi-threading:
> > memoization, which modifies the source code tree structure, is not
> > thread-safe.
>
> Yeah, at this point I think that you really should be using 2.0 if you
> a
Hi,
On Sat 03 Sep 2011 22:32, l...@gnu.org (Ludovic Courtès) writes:
> ri...@happyleptic.org skribis:
>
>>> For 1.8, could you try running Helgrind and see what happens?
>>
>> Helgrind complains about loads of 'possible data race'
>
> Actually 1.8 has a serious problem when it comes to multi-thre
Hi!
ri...@happyleptic.org skribis:
>> For 1.8, could you try running Helgrind and see what happens?
>
> Helgrind complains about loads of 'possible data race'
Actually 1.8 has a serious problem when it comes to multi-threading:
memoization, which modifies the source code tree structure, is not
t
-[ Fri, Sep 02, 2011 at 11:26:42AM +0200, ri...@happyleptic.org ]
> Or maybe the deadlock involves another lock in addition to
> this one. I'm going to turn scm_i_port_table_mutex into a recursive
> mutex in order to try to invalidate my theory.
initializing scm_i_port_table_mutex as a recursi
-[ Fri, Sep 02, 2011 at 11:26:42AM +0200, ri...@happyleptic.org ]
> > For 1.8, could you try running Helgrind and see what happens?
> ==26762== Thread #1: Exiting thread still holds 1 lock
> ==26762==at 0x5A81B4D: waitpid (waitpid.c:41)
> ==26762==by 0x4F0A289: scm_waitpid (posix.c:560)
> For 1.8, could you try running Helgrind and see what happens?
Helgrind complains about loads of 'possible data race' but does not
detect anything wrong when the actual deadlock occurs. When I exit
the program it does tell that a threads still own some lock, but
does not reveal the addresses of t
-[ 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
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?
> - more surprisingly, "gui
Should I file a bug report at savannah, then?
> > - all ports are closed, but what about other open files that are not
> > ports ? My application opens many files in C that are not known to
> > guile. Shouldn't these be closed as well ?
> >
> From this, I gather you have a C application that has Guile embedded,
> right?
Yes.
> (...) it c
ri...@happyleptic.org writes:
> Hello !
>
> Sometime, my progam calls open-input-pipe and the forked child hangs
> waiting for a lock (so after the fork but before executing the command).
>
> So I read the code for open-process, especially what happens between the
> fork and the execlp, and I noti
11 matches
Mail list logo
