[Soot-list] Exception Table

[Patrick Lam]

mbatch at cs.mcgill.ca wrote:
> Pat,
> 
> Sorry - I've been away from email for a few days. I did indeed make that
> patch due to a bug that was causing "holes" in the catch blocks, if I
> recall correctly. I don't remember the exact scenario, but as far as the
> claim that a store instruction will not cause an exception, that may be
> true, but you need to account for all throwables - including Errors and
> Asynchronous Exceptions.
> 
> I can look into this further unless the solution you've checked in solves
> people's problems. My patch obviously came about from obfuscation work, so
> I can say it might have been odd looking bytecode that I was dealing with
> - but it was definitely valid and verifiable bytecode. As noted, javac can
> and often does make odd looking bytecode out of constructs like
> synchronized blocks, where a catch block catches its own throwables.

My patch certainly fixes Silviu's problem. I don't know if it causes 
other problems down the line, though. It caused one problem in the abc 
suite, which I've since fixed. Someone should run the Soot test suites...

I think that my patch logically makes sense, but it might still be flawed.

pat