On 2011-01-21 04:44, Dima Pasechnik wrote:
> In my case abort() will happen for potentially many different reasons.
> So I'd like to have
>
> #include "c_lib/include/interrupt.h"
> char[1000] errmessage
> void libgap_errors()
> {
> set_sage_signal_handler_message(errmessage);
> abort();
> }
>
> and set errmessage in the Cython code.
> Will this work?
Yes, that would work.
> It would be even more natural to call set_sage_signal_handler_message
> after abort()
That will not be possible, because abort() invokes the signal handling
machinery which in turn then longjmp()s. So there is no "after abort()".
Jeroen.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
