Opened 12 years ago
Last modified 10 years ago
#171 new defect
Current code for handling lisp errors/NSExecptions in event thread is not robust.
| Reported by: | gb | Owned by: | gb |
|---|---|---|---|
| Priority: | normal | Milestone: | Cocoa IDE v1 |
| Component: | IDE | Version: | |
| Keywords: | Cc: |
Description
See ticket:145, ticket:139, and elsewhere.
The current code just tries to print an error message and a backtrace to the event thread's error/debug-io stream, but often craps out, failing to handle errors that occur while printing backtraces, entering a break loop on the event thread, etc.
This current scheme isn't really adequate for end users and is barely adequate for us, but anything better that we come up with will likely face many of the same issues that the current scheme is not handling properly.
Change History (1)
comment:1 Changed 10 years ago by jaj
- Milestone set to Cocoa IDE v1
- Priority changed from major to normal
Note: See
TracTickets for help on using
tickets.
This sort of looks like a duplicate for bug #145. I guess it's more specific. I will assume that gb knows how to reproduce it, and knows what to do about it. I'm changing it to normal priority rather than major, since it mainly affects people writing event handling code, not typical IDE users. If there are specific cases that happen NOT in user written event handlers, then we should open a bug for those cases and give them a major priority.