4 ms·
"Everything* just worked. We took a snapshot at 1.1.0, and we didn't update it. [* The JVM does SEGV on us occasionally. Internal error, which we have not dia
by richcollins 17y ago
"Everything* just worked. We took a snapshot at 1.1.0, and we didn't update it. [* The JVM does SEGV on us occasionally. Internal error, which we have not diagnosed.]"
How are memory protection errors just a footnote?
- cma 17y agoYou shouldn't be able to SEGV a JVM no matter what bytecode you feed it (exempting JNI). So it is a JVM bug.
- wmf 17y agoOTOH it doesn't really matter whose "fault" it is; if using Clojure causes SEGVs but some other Lisp doesn't cause SEGVs, that's a problem.
- yangyang 17y agoThat depends if you're using it primarily because it is a lisp or primarily because of its Java interop / the fact it runs on the JVM.
- Tichy 17y agoStill, if Sun doesn't fix it, then Clojure should provide a workaround.