Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

maxima sometimes isn't closed properly when wxMaxima crashes #409

Open
gunterkoenigsmann opened this issue Feb 8, 2015 · 1 comment
Open

maxima sometimes isn't closed properly when wxMaxima crashes #409

gunterkoenigsmann opened this issue Feb 8, 2015 · 1 comment
Labels
bug

Comments

@gunterkoenigsmann
Copy link
Member

Did experience this on the combination Windows/gcl. Now I did experience the same thing on the combination Linux/sbcl: If I start wxMaxima from a terminal and then interrupt it using Ctrl+C one CPU is running constantly thereafter. On my linux/sbcl version I get an endless stream of the following console output in this case:

   Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
   Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {1006CCED13}>
   Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
   Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {1006CCED13}>
   Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
   Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {1006CCED13}>

There seems to be no really portable way to catch a SIGSEV or similar, though.
@gunterkoenigsmann
Copy link
Member Author

The last commit didn't work => reopening.

@KubaO KubaO added the bug label Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gunterkoenigsmann @KubaO