Sjoerd van Leent :
>
> 2012/5/4 :
>> Message: 1
>> Date: Thu, 03 May 2012 21:47:28 +0200
>> From: l...@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=)
>> To: Andy Wingo
>> Cc: guile-devel@gnu.org
>> Subject: Re: Problems with compilation on Trisquel
Met vriendelijke groet,
Sjoerd
2012/5/4 :
> Message: 1
> Date: Thu, 03 May 2012 21:47:28 +0200
> From: l...@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=)
> To: Andy Wingo
> Cc: guile-devel@gnu.org
> Subject: Re: Problems with compilation on Trisquel 5.5
> Message-ID: &l
Andy Wingo skribis:
> On Wed 02 May 2012 23:15, l...@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo skribis:
>>
>>> Some versions of libgc do produce one SIGSEGV at startup, when
>>> determining certain aspects of the process's memory layout. Just FYI :)
>>
>> Woow. :-) Do you know which v
On Wed 02 May 2012 23:15, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> Some versions of libgc do produce one SIGSEGV at startup, when
>> determining certain aspects of the process's memory layout. Just FYI :)
>
> Woow. :-) Do you know which versions/arches are affected?
I
Hello!
Andy Wingo skribis:
> Some versions of libgc do produce one SIGSEGV at startup, when
> determining certain aspects of the process's memory layout. Just FYI :)
Woow. :-) Do you know which versions/arches are affected?
Thanks,
Ludo’.
Hi Ludo, Andy,
I am writing down where the error exactly originates, together with
possible other findings such as backtraces, etc.
The first initiation of GUILD goes wrong in the make process itself,
generating guile-procedures.texi. A condensed version of the error
reported is (full error repor
On Wed 25 Apr 2012 22:42, l...@gnu.org (Ludovic Courtès) writes:
>> and eventually ends up with a SIGSEGV message from the procedure:
>> GC_generic_malloc_inner.
>
> Could you show the backtrace?
>
> This is with libgc 7.1, right?
Some versions of libgc do produce one SIGSEGV at startup, when
det
Hi,
Sjoerd van Leent skribis:
> When compiling I get to the generation stage of GEN guile-procedures.texi.
> The stage ends up with a Segmentation fault. I have been debugging the
> lt_guile process with gdb, and some interesting things happened. The
> process received SIGPWR and SIGXCPU signals
I found out, as a response to myself that the tag guile-2.0.5 does not
share the same issues as the master branch. I will attempt to figure out
where and when the problem is introduced, but it will be helpful if anyone
knows about a change which might involve different/weird GC behavior.
Regards,
