You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The segfault is caught and handled by cysignals, but from thereafter other GAP errors result in a segfault as well.
However, replacing gap.Sum(*x) with gap.eval('Sum(0, 1, 2)'), although still resulting in a GAPError, does not appear to lead to this condition. So I think the bug is probably local to GapFunction.__call__. Though it's weird that it breaks all error handling.
The text was updated successfully, but these errors were encountered:
The following code, adapted from the doctests, results in a segfault:
The segfault is caught and handled by cysignals, but from thereafter other GAP errors result in a segfault as well.
However, replacing
gap.Sum(*x)
withgap.eval('Sum(0, 1, 2)')
, although still resulting in aGAPError
, does not appear to lead to this condition. So I think the bug is probably local toGapFunction.__call__
. Though it's weird that it breaks all error handling.The text was updated successfully, but these errors were encountered: