#14029: Exit Sage ungracefully upon SIGQUIT
----------------------------------+-------------------------------
Reporter: jdemeyer | Owner: jdemeyer
Type: enhancement | Status: positive_review
Priority: major | Milestone: sage-5.13
Component: c_lib | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers: Peter Bruin
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: #13908, #13996 | Stopgaps:
----------------------------------+-------------------------------
Comment (by jdemeyer):
Replying to [comment:7 pbruin]:
> The fact that `sage-CSI` is run does mean that if GDB is available, it
now takes about 10 seconds before you are back at the shell. Pressing
`^\` a second time does not immediately interrupt `sage-CSI`. I'm not
sure why; is the `^\` somehow intercepted by GDB? Pressing `^C` during
these 10 seconds does generate a Python `KeyboardInterrupt` in `sage-CSI`,
but does not immediately get you back to the shell either.
That's right indeed. It seems that, once GDB gets hold of a process, there
is no easy way to get out.
--
Ticket URL: <http://trac.sagemath.org/ticket/14029#comment:8>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.