#8 deadlock detection
Hello,
With the attached code, I tested two scenarios:
1) I call grabB from within grabAB.
Then I get the following output
D:\marc\workspace\JLintTest>jlint -source src bin
src\com\zappware\test\JLintTest.java:75: Lock
com/zappware/test/JLintTest.A is r
equested while holding lock
com/zappware/test/JLintTest, with other thread holdi
ng com/zappware/test/JLintTest.A and requesting lock
com/zappware/test/JLintTest
.
src\com\zappware\test\JLintTest.java:67: Lock
com/zappware/test/JLintTest.B is r
equested while holding lock
com/zappware/test/JLintTest.A, with other thread hol
ding com/zappware/test/JLintTest.B and requesting
lock com/zappware/test/JLintTe
st.A.
Verification completed: 2 reported messages.
2) I call grabB from within f1
Then I get
D:\marc\workspace\JLintTest>jlint -source src bin
Verification completed: 0 reported messages.
Is this a bug or a known limitation?
Kind regards,
Marc
test code