[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Exceptions in Soot
Offhand, I can think of two possiblities:
- dump out Soot's internal state
and some context information (e.g.,
died while processing this statement in
this method of this class)
- drop into a debugger such as BeanShell
or Jython.
Manoj
Ondrej Lhotak wrote (Tue, Aug 19, 2003 at 08:21:32PM -0400) :
> There was such a thing: CompilationDeathException. However, lots of
> people didn't use it, possibly because it was so long to type. In most
> cases where RuntimeException is used, it signals something that
> shouldn't ever happen (basically an assertion failure), rather than
> a user error.
>
> What would you suggest that Soot do with a SootException (customized by
> options), other than the current stack trace and abort?
>
> Ondrej
>
> On Tue, Aug 19, 2003 at 06:12:17PM -0500, Manoj Plakal wrote:
> >
> > I've noticed that Soot throws
> > a bare RuntimeException in many
> > places to signal an error.
> >
> > Have you considered throwing
> > your own SootException and have
> > it's behavior be customized with
> > Soot options? E.g., perhaps
> > you could be dropped into a
> > Beanshell instance to inspect
> > heap-resident data (I do this
> > right now with my Soot phases).
> >
> > Manoj
> >