#35
- Created on2007-08-31 16:29
- Reported by
- StatusInvalid
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
Presentation compiler dies silently and produces no output nor error
Migrated from http://lampsvn.epfl.ch/trac/scala/ticket/35
Reporter dragos
A crash of the presentation compiler may go unnoticed, showing no errors nor warnings. Even though the error log has an entry, it takes a bit of time to realize what's going on. A crash should be reported along with normal compiler errors (something like 'internal compiler error').
Reporter dragos
A crash of the presentation compiler may go unnoticed, showing no errors nor warnings. Even though the error log has an entry, it takes a bit of time to realize what's going on. A crash should be reported along with normal compiler errors (something like 'internal compiler error').
Leave a comment
Trac author: mcdirmid
An error dialogue box is put up for the first crash/error log entry. If we did it for every crash, the UI could get locked up really quickly, as the plugin crashes a lot. This is the best way to deal with the compiler (build and presentation), which is unstable and crashes alot.
An error dialogue box is put up for the first crash/error log entry. If we did it for every crash, the UI could get locked up really quickly, as the plugin crashes a lot. This is the best way to deal with the compiler (build and presentation), which is unstable and crashes alot.
on 2008-04-08 22:50 *
By tracImporter
Closed As: wontfix
