-
I can confirm that just removing that line also produces code that actually runs.
2009-11-07 20:42:09 UTC in ProGuard Java Optimizer and Obfuscator
-
I assume you mean MONITOREXIT, but yes, I believe that would work. That was actually the solution proposed by one of my colleagues, but I thought it better (in light of the aforementioned discussions) to make the minimum changes required to the class files in order to get them to run correctly. I'm happy to test any patches.
Another potential source of exceptions in MONITOREXIT is asynchronous...
2009-11-07 20:26:18 UTC in ProGuard Java Optimizer and Obfuscator
-
All modern Java compilers (Sun JDK compilers since 1.4, gcj, jikes, and others) add an exception table entry around the monitorexit instruction in the exception handler for a synchronized block. This triggers a bug in the JIT compiler used in Sun JRE's up to at least version 1.2, causing the code to enter an infinite loop, throwing IllegalMonitorStateExceptions. Thus, code produced with -target...
2009-11-06 04:58:13 UTC in ProGuard Java Optimizer and Obfuscator
-
tterribe committed revision 16 to the CMR-rep SVN repository, changing 2 files.
2008-01-31 00:40:47 UTC in CMR-rep
-
tterribe committed revision 15 to the CMR-rep SVN repository, changing 5 files.
2008-01-30 03:12:42 UTC in CMR-rep
-
tterribe committed revision 14 to the CMR-rep SVN repository, changing 1 files.
2008-01-28 06:45:18 UTC in CMR-rep
-
tterribe committed revision 13 to the CMR-rep SVN repository, changing 1 files.
2007-10-13 21:15:03 UTC in CMR-rep
-
tterribe committed revision 12 to the CMR-rep SVN repository, changing 1 files.
2007-10-13 21:01:29 UTC in CMR-rep
-
tterribe committed revision 11 to the CMR-rep SVN repository, changing 2 files.
2007-09-25 23:26:27 UTC in CMR-rep
-
tterribe committed revision 10 to the CMR-rep SVN repository, changing 2 files.
2007-09-25 22:39:33 UTC in CMR-rep
