libGAP error handling bug

[jdemeyer]

The libGAP error handler (error_handler()) in sage/libs/gap/util.pyx should use set_sage_signal_handler_message() instead of sig_str(). Unfortunately, this exposes a bug in GCC-4.8.0: #14460 (work-around: compile with -fno-tree-dominator-opts).

CC: @vbraun

Component: interfaces

Author: Jeroen Demeyer

Reviewer: Volker Braun

Merged: sage-5.10.beta0

Issue created by migration from https://trac.sagemath.org/ticket/14453

[jdemeyer]

comment:1

Attachment: sage_crash_ihsJs4.log

[jdemeyer]

comment:3

Looks like a GCC compiler bug (GCC-4.8.0).

[vbraun]

comment:7

Thanks for debugging this! Should we still treat this as critical or maybe just wait until gcc-4.8.1 is out?

[jdemeyer]

comment:8

Independently of the GCC issue, there still is a segmentation fault with Cython-0.19b2. Perhaps we should also fix that here.

[jdemeyer]

comment:10

The Cython segfault also looks like an upstream (Cython-0.19b2) problem. So libGAP does a good job of testing various upstream projects :-)

[jdemeyer]

Author: Jeroen Demeyer

[jdemeyer]

comment:11

Modulo upstream issues, this patch should be fine and can be applied.

[jdemeyer]

comment:12

Attachment: 14453_libgap.patch.gz

The critical bug is #14460.

[vbraun]

Reviewer: Volker Braun

[vbraun]

comment:13

Looks good to me.

[jdemeyer]

Merged: sage-5.10.beta0