GNU bug report logs - #29256
maxima: The SGC segfault recovery test failed with memprotect_bad_fault_address, SGC disabled

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29256 in the body.
You can then email your comments to 29256 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Alex Vong <alexvong1995 <at> gmail.com>
To: bug-guix <at> gnu.org, guix-devel <at> gnu.org
Subject: maxima: The SGC segfault recovery test failed with
 memprotect_bad_fault_address, SGC disabled
Date: Sat, 11 Nov 2017 18:50:26 +0800

[Message part 1 (text/plain, inline)]

Hello all,

When I start maxima, I get the following warning message:

The SGC segfault recovery test failed with memprotect_bad_fault_address, SGC disabled
The SGC segfault recovery test failed with memprotect_bad_fault_address, SGC disabled
Maxima 5.41.0 http://maxima.sourceforge.net
using Lisp GNU Common Lisp (GCL) GCL 2.6.12
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.

Actually I encountered this problem quite a while ago after an update,
but I didn't report it since it was not fetal.

Does anyone knows what's going on?

Cheers,
Alex

[signature.asc (application/pgp-signature, inline)]

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Kei Kebreau <kkebreau <at> posteo.net>
To: Alex Vong <alexvong1995 <at> gmail.com>
Cc: guix-devel <at> gnu.org, bug-guix <at> gnu.org
Subject: Re: maxima: The SGC segfault recovery test failed with
 memprotect_bad_fault_address, SGC disabled
Date: Tue, 14 Nov 2017 12:38:53 -0500

[Message part 1 (text/plain, inline)]

Alex Vong <alexvong1995 <at> gmail.com> writes:

> Hello all,
>
> When I start maxima, I get the following warning message:
>
> The SGC segfault recovery test failed with
> memprotect_bad_fault_address, SGC disabled
> The SGC segfault recovery test failed with
> memprotect_bad_fault_address, SGC disabled
> Maxima 5.41.0 http://maxima.sourceforge.net
> using Lisp GNU Common Lisp (GCL) GCL 2.6.12
> Distributed under the GNU Public License. See the file COPYING.
> Dedicated to the memory of William Schelter.
> The function bug_report() provides bug reporting information.
>
> Actually I encountered this problem quite a while ago after an update,
> but I didn't report it since it was not fetal.

When did you first notice this issue?

>
> Does anyone knows what's going on?
>
> Cheers,
> Alex

Hello Alex,

This is my first time running into this issue. While I do get this
warning message using the Maxima substitute from hydra.gnu.org, when I
build Maxima 5.41.0 from source locally, this warning message does not
appear. Is this the case for you as well?

The message comes from the source code of GNU Common Lisp, but the GCL
binary from hydra.gnu.org doesn't give this error when I run it. It
seems like this comes down a bug in GCL set off by Maxima, a bug in
Maxima, a reproducibility issue, or some combination of all of
these. I'll be investigating this further.

Thank you,
Kei

[signature.asc (application/pgp-signature, inline)]

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Alex Vong <alexvong1995 <at> gmail.com>
To: Kei Kebreau <kkebreau <at> posteo.net>
Cc: guix-devel <at> gnu.org, bug-guix <at> gnu.org
Subject: Re: maxima: The SGC segfault recovery test failed with
 memprotect_bad_fault_address, SGC disabled
Date: Fri, 17 Nov 2017 01:32:39 +0800

[Message part 1 (text/plain, inline)]

Kei Kebreau <kkebreau <at> posteo.net> writes:

> Alex Vong <alexvong1995 <at> gmail.com> writes:
>
>> Hello all,
>>
>> When I start maxima, I get the following warning message:
>>
>> The SGC segfault recovery test failed with
>> memprotect_bad_fault_address, SGC disabled
>> The SGC segfault recovery test failed with
>> memprotect_bad_fault_address, SGC disabled
>> Maxima 5.41.0 http://maxima.sourceforge.net
>> using Lisp GNU Common Lisp (GCL) GCL 2.6.12
>> Distributed under the GNU Public License. See the file COPYING.
>> Dedicated to the memory of William Schelter.
>> The function bug_report() provides bug reporting information.
>>
>> Actually I encountered this problem quite a while ago after an update,
>> but I didn't report it since it was not fetal.
>
> When did you first notice this issue?
>
I am afraid I cannot remember exactly when...

I installed wxmaxima long ago and things worked fine for a long
time. One day, after updating wxmaxima, it showed the above warning and
started to crash nondeterministically when I typed things into the
message box. The crash was fixed quickly by another update, but the
warning persisted. 

>>
>> Does anyone knows what's going on?
>>
>> Cheers,
>> Alex
>
> Hello Alex,
>
> This is my first time running into this issue. While I do get this
> warning message using the Maxima substitute from hydra.gnu.org, when I
> build Maxima 5.41.0 from source locally, this warning message does not
> appear. Is this the case for you as well?
>
Same for me. I set --prefix during configure and install it
somewhere. It starts without the warning.

> The message comes from the source code of GNU Common Lisp, but the GCL
> binary from hydra.gnu.org doesn't give this error when I run it. It
> seems like this comes down a bug in GCL set off by Maxima, a bug in
> Maxima, a reproducibility issue, or some combination of all of
> these. I'll be investigating this further.
>
> Thank you,
> Kei

Thanks for looking at it!

[signature.asc (application/pgp-signature, inline)]

Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Kei Kebreau <kkebreau <at> posteo.net>
To: Alex Vong <alexvong1995 <at> gmail.com>
Cc: guix-devel <at> gnu.org, bug-guix <at> gnu.org
Subject: Re: maxima: The SGC segfault recovery test failed with
 memprotect_bad_fault_address, SGC disabled
Date: Wed, 22 Nov 2017 12:42:44 -0500

[Message part 1 (text/plain, inline)]

Alex Vong <alexvong1995 <at> gmail.com> writes:

> Kei Kebreau <kkebreau <at> posteo.net> writes:
>
>> Alex Vong <alexvong1995 <at> gmail.com> writes:
>>
>>> Hello all,
>>>
>>> When I start maxima, I get the following warning message:
>>>
>>> The SGC segfault recovery test failed with
>>> memprotect_bad_fault_address, SGC disabled
>>> The SGC segfault recovery test failed with
>>> memprotect_bad_fault_address, SGC disabled
>>> Maxima 5.41.0 http://maxima.sourceforge.net
>>> using Lisp GNU Common Lisp (GCL) GCL 2.6.12
>>> Distributed under the GNU Public License. See the file COPYING.
>>> Dedicated to the memory of William Schelter.
>>> The function bug_report() provides bug reporting information.
>>>
>>> Actually I encountered this problem quite a while ago after an update,
>>> but I didn't report it since it was not fetal.
>>
>> When did you first notice this issue?
>>
> I am afraid I cannot remember exactly when...
>
> I installed wxmaxima long ago and things worked fine for a long
> time. One day, after updating wxmaxima, it showed the above warning and
> started to crash nondeterministically when I typed things into the
> message box. The crash was fixed quickly by another update, but the
> warning persisted. 
>
>>>
>>> Does anyone knows what's going on?
>>>
>>> Cheers,
>>> Alex
>>
>> Hello Alex,
>>
>> This is my first time running into this issue. While I do get this
>> warning message using the Maxima substitute from hydra.gnu.org, when I
>> build Maxima 5.41.0 from source locally, this warning message does not
>> appear. Is this the case for you as well?
>>
> Same for me. I set --prefix during configure and install it
> somewhere. It starts without the warning.
>
>> The message comes from the source code of GNU Common Lisp, but the GCL
>> binary from hydra.gnu.org doesn't give this error when I run it. It
>> seems like this comes down a bug in GCL set off by Maxima, a bug in
>> Maxima, a reproducibility issue, or some combination of all of
>> these. I'll be investigating this further.
>>
>> Thank you,
>> Kei
>
> Thanks for looking at it!

I turns out that the issue is with stratified garbage collection in
GCL. The substitute from hydra.gnu.org does in fact give me the error
when I run "(si::sgc-on t)" in the REPL. I'm preparing a patch to update
GCL to the version used in Debian stable (GCL git tag "pathnames1.13") and
we'll see if changing that definition on the master branch will do anything.

[signature.asc (application/pgp-signature, inline)]

Message #17 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Kei Kebreau <kkebreau <at> posteo.net>
To: Alex Vong <alexvong1995 <at> gmail.com>
Cc: guix-devel <at> gnu.org, bug-guix <at> gnu.org
Subject: Re: maxima: The SGC segfault recovery test failed with
 memprotect_bad_fault_address, SGC disabled
Date: Wed, 22 Nov 2017 12:46:06 -0500

[Message part 1 (text/plain, inline)]

Kei Kebreau <kkebreau <at> posteo.net> writes:
>
> I turns out that the issue is with stratified garbage collection in
> GCL. The substitute from hydra.gnu.org does in fact give me the error
> when I run "(si::sgc-on t)" in the REPL. I'm preparing a patch to update
> GCL to the version used in Debian stable (GCL git tag "pathnames1.13") and
> we'll see if changing that definition on the master branch will do anything.

On second thought, the patches applied to Debian Sid's GCL look useful
as well. Anyway, keep an eye out for my update patch.

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 29256-done <at> debbugs.gnu.org (full text, mbox):

From: Alex Vong <alexvong1995 <at> gmail.com>
To: Kei Kebreau <kkebreau <at> posteo.net>
Cc: guix-devel <at> gnu.org, 29256-done <at> debbugs.gnu.org
Subject: Re: maxima: The SGC segfault recovery test failed with
 memprotect_bad_fault_address, SGC disabled
Date: Sat, 25 Nov 2017 22:15:06 +0800

[Message part 1 (text/plain, inline)]

Kei Kebreau <kkebreau <at> posteo.net> writes:

> Kei Kebreau <kkebreau <at> posteo.net> writes:
>>
>> I turns out that the issue is with stratified garbage collection in
>> GCL. The substitute from hydra.gnu.org does in fact give me the error
>> when I run "(si::sgc-on t)" in the REPL. I'm preparing a patch to update
>> GCL to the version used in Debian stable (GCL git tag "pathnames1.13") and
>> we'll see if changing that definition on the master branch will do anything.
>
> On second thought, the patches applied to Debian Sid's GCL look useful
> as well. Anyway, keep an eye out for my update patch.

Thank you! The patch works, the warning has gone. I am closing this bug.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.