Opened 6 years ago
Last modified 2 months ago
#20024 new defect
Fix infinite crash loop when quitting gp interpreter
Reported by: | vdelecroix | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | sage-9.5 |
Component: | interfaces | Keywords: | pari, gp, console |
Cc: | jdemeyer, slelievre | Merged in: | |
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
sage: %gp pari: quit PARI/GP interpreter crashed -- automatically restarting. PARI/GP interpreter crashed -- automatically restarting. PARI/GP interpreter crashed -- automatically restarting. PARI/GP interpreter crashed -- automatically restarting. ...
Initially reported in this question on ask.sagemath.org
Change History (6)
comment:1 Changed 6 years ago by
- Description modified (diff)
comment:2 Changed 2 years ago by
comment:3 Changed 13 months ago by
- Cc jdemeyer slelievre added
- Keywords pari gp console added
- Milestone changed from sage-7.1 to sage-9.3
- Priority changed from critical to major
The proper way to exit the gp console seems to be Ctrl
+ D
.
sage: %gp --> Switching to PARI/GP interpreter <-- pari: <Ctrl + D> --> Exiting back to Sage <-- sage:
Should this be documented somewhere?
Can we prevent the infinite loop and make
quit
behave the same as Ctrl
+ D
?
Demoting from 'critical' to 'major'.
Version 0, edited 13 months ago
by
(next)
comment:4 Changed 13 months ago by
- Summary changed from can not quit gp interpreter to Fix infinite crash loop when quitting gp interpreter
comment:5 Changed 7 months ago by
- Milestone changed from sage-9.3 to sage-9.4
Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date.
comment:6 Changed 2 months ago by
- Milestone changed from sage-9.4 to sage-9.5
Note: See
TracTickets for help on using
tickets.
Part of this is normal. Quitting works when using
Whereas
%gp
is an interactive access to the unique pari/gp session used by sage, which is automatically restarted when crashed.What is not normal is the infinite restarting loop..