Re: Core Exception Throwing and Handling

[Phil Muldoon <pmuldoon at redhat dot com>]

Yao Qi wrote:
> > If ftrace or the UI gets a negative syscall runtime exception should it 
> > quit? Like lots of other exceptions it's wrapped in a Runtime exception 
> > and thrown.
> >     
>
> we could set up a new class SyscallException to handle this, and
> replace RuntimeException with SyscallException.
>
> IMO, ftrace or the UI could *not* quit when they get negative syscall
> runtime exception, could skip this negative syscall, report or log
> something, and continue.
>   

Would that be a checked exception?

> It was discussed here,
> http://sources.redhat.com/ml/frysk/2006-q3/msg00090.html
>
>   
Right but not really resolved. It's been a long term issue about how the 
ui should handle core oops. As we have more core clients it becomes more 
important and harder to backport changes if required.

Regards

Phil