We've experienced the `java.lang.IllegalMonitorStateException: current
thread not owner' exception after we run some of our test programs through
Soot, our Java bytecode analysis framework. Strangely enough, the
exception does not occur on the original copies of the programs, only
after we Sootify.
At first, I thought this was a problem with Soot, but the error seems to
be the same one people are encountering without Sootifying their files.
We are running Debian potato on 2.2.8 kernels, Blackdown's JDK1.2.2, with
native threads, on dual-processor PII systems.
pat
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
