[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: swig failure on aarch64 on core-updates

From: Ludovic Courtès
Subject: Re: swig failure on aarch64 on core-updates
Date: Thu, 22 Nov 2018 09:56:18 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Efraim Flashner <address@hidden> skribis:

> On Sun, Nov 18, 2018 at 09:35:51AM +0200, Efraim Flashner wrote:
>> From the build log with --cores=1
>> checking guile testcase template_whitespace
>> checking guile testcase threads
>> checking guile testcase threads_exception
>> checking guile testcase throw_exception (with run test)
>> free(): invalid pointer
>> /gnu/store/3dzvi613nf3fz42rabksw6svslvanfz7-bash-minimal-4.4.23/bin/sh: line 
>> 1: 21784 Aborted                 (core dumped) env GUILE_AUTO_COMPILE=0 
>> /gnu/store/7pb9ywfzvr8jwgykpj52vfd8d6kimc3w-guile-2.0.14/bin/guile -l .
>> /throw_exception_runme.scm
>> make[1]: *** [Makefile:36: throw_exception.cpptest] Error 134
>> checking guile testcase typedef_array_member
>> checking guile testcase typedef_class
>> checking guile testcase typedef_funcptr
>> checking guile testcase typedef_inherit (with run test)
>> checking guile testcase typedef_mptr
>> I don't see anything upstream about this, so I figured I'd post it here
>> first. This happens with and without the fix-swig-for-i686 patch.
> I don't know what's different about today, but swig built with no
> problems while I was test building my profile on core-updates.

The thing actually aborted (SIGABRT):

--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (status:term-sig 134)
$3 = 6
scheme@(guile-user)> SIGABRT
$4 = 6
--8<---------------cut here---------------end--------------->8---

So I guess this could have been caused by an OOM condition.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]