Re: [Pharo-users] global exception handler mechanism

2018-02-16 Thread Norbert Hartl
> Am 16.02.2018 um 13:38 schrieb Henrik Sperre Johansen > : > > You can also override #defaultAction on Exception, and install a custom > UIManager subclass implementing unhandledErrorDefaultAction: (sent by > UnhandledError #defaultAction, receives the error as

Re: [Pharo-users] global exception handler mechanism

2018-02-16 Thread Henrik Sperre Johansen
You can also override #defaultAction on Exception, and install a custom UIManager subclass implementing unhandledErrorDefaultAction: (sent by UnhandledError #defaultAction, receives the error as argument). Would be nice(r) if UIManager had a defaultUnhandledErrorActionBlock: setter, but it's not

Re: [Pharo-users] global exception handler mechanism

2018-02-15 Thread Denis Kudriashov
Hi 2018-02-05 11:00 GMT+01:00 Igor Stasenko : > > > On 5 February 2018 at 10:17, Marcus Denker wrote: > >> Hello, >> >> The Sunit-Debugger does a stack search on startup to find the test >> related exception. >> >> It might be good to do it better,

Re: [Pharo-users] global exception handler mechanism

2018-02-05 Thread Igor Stasenko
On 5 February 2018 at 10:17, Marcus Denker wrote: > Hello, > > The Sunit-Debugger does a stack search on startup to find the test related > exception. > > It might be good to do it better, especially as the debug process starts > from the exception > I might be a good

Re: [Pharo-users] global exception handler mechanism

2018-02-05 Thread Marcus Denker
Hello, The Sunit-Debugger does a stack search on startup to find the test related exception. It might be good to do it better, especially as the debug process starts from the exception I might be a good idea to actually keep a reference to it. Would there be any downside of Exception>>debug

[Pharo-users] global exception handler mechanism

2018-02-02 Thread Peter Uhnák
Hi, is there a way to install a global handler for exceptions? Right now if I want to log all exceptions, I use approach from ShoreLine and create a PreDebugAction which is activated when any "unhandled" exception occurs. That would be good enough, however the Debugger has zero knowledge of the