Issue 4954 in pharo: MorphicUIManager shall attempt to log the error before opening the UI

Status: Accepted
Owner: [hidden email]
Labels: Type-Feature Milestone-1.4

New issue 4954 by [hidden email]: MorphicUIManager shall attempt to  
log the error before opening the UI
http://code.google.com/p/pharo/issues/detail?id=4954

I made this change in Squeak.
If debugger open fails (2nd bug), then we get an emergency evaluator and  
can hardly track the origin of the 1st bug.
If we write first, than at least, it gives us a chance to track the 1st  
problem when the UI fails to open.




_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: Importance-High

Comment #1 on issue 4954 by [hidden email]: MorphicUIManager shall  
attempt to log the error before opening the UI
http://code.google.com/p/pharo/issues/detail?id=4954

More over, scripting to the log shall be protected against error, otherwise  
there is a recursive error...
I killed Pharo process several times this evening so I think like  
encouraged to commit a SLICE ;)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixReviewNeeded

Comment #2 on issue 4954 by [hidden email]: MorphicUIManager shall  
attempt to log the error before opening the UI
http://code.google.com/p/pharo/issues/detail?id=4954

Name:  
SLICE-Issue-4954-MorphicUIManager-shall-attempt-to-log-the-error-before-opening-the-UI-nice.1
Author: nice
Time: 31 October 2011, 10:01:30 pm
UUID: dbdd9d23-6176-436f-9bf7-a966cf5d4abb
Ancestors:
Please, review this one, it might improve experience of brave souls  
fighting bugs in bleeding edge Pharo.

Dependencies: Polymorph-Widgets-nice.537

Log the error to error file before opening the debugger UI.
RATIONALE: if a secondary Error happens while opening the debugger, it's  
usefull to at least find a log of the primary Error.

Protect the writing to error file from Error.
RATIONALE: this feature is intended as a helper, not a killer of your image  
by virtue of recursive Error...


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Cc: [hidden email]

Comment #3 on issue 4954 by [hidden email]: MorphicUIManager shall  
attempt to log the error before opening the UI
http://code.google.com/p/pharo/issues/detail?id=4954

Igor can you review this code


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixToInclude

Comment #4 on issue 4954 by [hidden email]: MorphicUIManager shall  
attempt to log the error before opening the UI
http://code.google.com/p/pharo/issues/detail?id=4954

makes sense.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Integrated

Comment #5 on issue 4954 by [hidden email]: MorphicUIManager shall  
attempt to log the error before opening the UI
http://code.google.com/p/pharo/issues/detail?id=4954

in 14247


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker