| Newsgroups |
gmane.comp.java.vm.sablevm.bugs |
| Message-ID |
<[email protected]> |
http://sablevm.org/bugs/show_bug.cgi?id=60
------- Additional Comments From [email protected] 2005-01-29 12:26 -------
Chris,
Actually, it would help, unless there's a serious bug in SableVM.
You just didn't notice that SableVM never sleeps while "running java". In other
words, before waiting/sleeping (for any reason, including contention), sablevm
calls _svmf_stopping_java(). So, using stop-the-world would simply insure that
no thread is "running java" (and they are prevented from resuming java), so the
"current" thread can safely read the stack structures of other threads for
printing the traces.
Remains two "little" problems:
1- what should the code do if the "current thread" is not attached to the VM?
2- what should the code do if there are actually many concurrent VMs in this
process (yes, this should be happening soon).
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.