Status fields:
| creation_ts: | 2005-07-22 02:54 |
|---|---|
| component: | vm |
| version: | unspecified |
| rep_platform: | All |
| op_sys: | Linux |
| bug_status: | REOPENED |
| reporter: | greenrd@greenrd.org |
It would be useful for the SIGQUIT handler to print - in addition to the stack traces that it currently prints - IDs of monitors held by, and being waited for by, each thread. I just encountered a VM deadlock and this might have helped me diagnose it.
I agree, that would be really useful. I'm not sure yet how it can be done. I'll look into it.
cacaojvm.org
This is one of the cases where the spec contradicts itself:
[from Section 4.9.1 The Verification Process]
Pass 4:
For efficiency reasons, certain tests that could in principle be performed
in Pass 3 are delayed until the first time the code for the method is
actually invoked. In so doing, Pass 3 of the verifier avoids loading class
files unless it has to.
In fact it's not only for efficiency but correctness. There is a lot of code
out there that assumes that only code which is actually executed is verified.
(And only *when* it is executed for the first time.)
Sorry, the last comment was meant for a different bug.
Sorry, actually it's not implemented.