Andy Wingo skribis:
> On Sun 09 Jun 2013 22:33, l...@gnu.org (Ludovic Courtès) writes:
>
>> However, that warning doesn’t take into account the signal thread, nor
>> the GC thread (if any). So, although that seems unlikely, there could
>> still be issues, for instance if the ‘scm_fork’ call happ
On Sun 09 Jun 2013 22:33, l...@gnu.org (Ludovic Courtès) writes:
> However, that warning doesn’t take into account the signal thread, nor
> the GC thread (if any). So, although that seems unlikely, there could
> still be issues, for instance if the ‘scm_fork’ call happens while
> ‘signal_delivery
Eli Zaretskii skribis:
> There's only one thread at this point, its backtrace is below.
> Actually, I don't see more than this one thread during the entire run
> (GDB doesn't announce any thread birth or death, and Process Explorer
> shows a single thread in the process at all times). Note that
> Date: Fri, 07 Jun 2013 17:59:57 +0300
> From: Eli Zaretskii
> Cc: guile-user@gnu.org
>
> > > What's more, after this backtrace is displayed, guile hangs here:
> > >
> > > void
> > > scm_i_close_signal_pipe()
> > > {
> > >/* SIGNAL_DELIVERY_THREAD_MUTEX is only locked whil
Here is a really small patch for guile-figl that fixes errors when
generating docs from texinfo files.
---
doc/gl.texi | 2 +-
doc/low-level-gl.texi | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/doc/gl.texi b/doc/gl.texi
index 0c77e8f..b0d6f01 100644
--- a/do
