Richard Braun skribis:
> Actually, it has nothing to do with Mach. What happens is that, when
> catching one of the SIGUSR signals (SIGUSR1 i guess), the process calls
> sigsuspend, waiting for the next (probably SIGUSR2). But when returning
> from the handler (in sigreturn), the sigcontext is NU
On Fri, Feb 08, 2013 at 07:08:05PM +0100, Gabriel Schnoering wrote:
> And running various version of guile both with libgc 7.1-9.1,
> problems still occur.
> It seems that libgc will trigger some issue with signal handling and mach.
>
> Here are the gdb logs for the guile packed with Debian.
> (no
Hi,
After some more investigation (especially by Richard Braun)
And running various version of guile both with libgc 7.1-9.1,
problems still occur.
It seems that libgc will trigger some issue with signal handling and mach.
Here are the gdb logs for the guile packed with Debian.
(not sure it is o
