At Sat, 2 Feb 2013 23:24:38 +0100,
Richard Braun wrote:
> On Sat, Feb 02, 2013 at 07:51:38PM +0100, Gabriel Schnoering wrote:
> > I can't run guile in gdb as there are some error with the garbage
> > collector.
>
> These are probably not errors. Many language interpretors rely on
> receiving SIGSE
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
Alle lunedì 4 febbraio 2013, Ludovic Courtès ha scritto:
> Richard Braun skribis:
> > On Sat, Feb 02, 2013 at 07:51:38PM +0100, Gabriel Schnoering wrote:
> >> I can't run guile in gdb as there are some error with the garbage
> >> collector.
> >
> > These are probably not errors.
>
> Indeed, you
Richard Braun skribis:
> On Sat, Feb 02, 2013 at 07:51:38PM +0100, Gabriel Schnoering wrote:
>> I can't run guile in gdb as there are some error with the garbage
>> collector.
>
> These are probably not errors.
Indeed, you need to let a couple of signals through:
handle SIGPWR noprint nostop
Hi,
As was discussed on irc, I investigated a bit deeper the issue.
First I compiled libgc-7.2d
./configure
make
make check
All tests passed ! (which was not the case with guile-2.0.7)
But make install failed for --prefix in the user ~/devel/libgc directory
(see hurdlibgcinstall)
Anyway I ra
On Sat, Feb 02, 2013 at 07:51:38PM +0100, Gabriel Schnoering wrote:
> I can't run guile in gdb as there are some error with the garbage
> collector.
These are probably not errors. Many language interpretors rely on
receiving SIGSEGV to implement memory. Use the gdb "handle" command to
make it auto
Hi, everyone.
I see that some people are excited by guile and the hurd.
So I'm coming here to break a bit the good mood, sorry for that.
I'm still stuck with the following issue I guess bug#11776: Guile with Hurd.
Running the following command in the shell
$ guile -c '(display (+ 1 2) (
