[Bug 92] threading is broken (most visible on SMP)

[email protected]
Newsgroups gmane.comp.java.vm.sablevm.bugs
Message-ID <[email protected]>
http://sablevm.org/bugs/show_bug.cgi?id=92





------- Additional Comments From [email protected]  2005-01-31 20:40 -------
It appears that this patch eliminated the assertion failure in the locking code
on i386 when combined with the JSR133 memory barriers, but not on x86_64.  This
is probably due to a bad memory barrier implementation on x86_64 (I used
_svmm_compare_and_swap as a default, but maybe either C&S is itself unsafe or
the MB needs stronger guarantees than those provided by C&S).

The other null pointer exceptions and assertion failures remain.

I also noticed a new assertion failure, but it probably was present before:

sablevm: local_refs.c:111: _svmh_new_native_local: Assertion
`native_local->previous == ((void *)0)' failed.

Thanks for this fix.  The JSR133 stuff is fairly ready to go into staging
sometime, but doing it will take time.  I still think a finite state machine
model of the locking algorithm would be valuable and also better than human
auditing.




------- 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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.