3 ms·
I appreciate you replying, and my sympathies for the posting weirdness - I was worried that I had inadvertently caused a karma trap. From what I recall (it's b
by ShroudedNight 3y ago
I appreciate you replying, and my sympathies for the posting weirdness - I was worried that I had inadvertently caused a karma trap.
From what I recall (it's been ~ 5 years), at least on OpenJ9, the potential SIGSEGV's for null references occurred in code generated by our JIT compiler, or in hand-rolled assembly, and not in code generated by any C translation unit. This may well not satisfy the standard, but honestly, at that point, I'm not sure any FFI-linked code will.
If you find this distinction insufficient, and still require the use of a JVM, if my memory serves correctly, -Xrs on OpenJ9 will avoid using those trap handlers. I don't believe this is true of Hotspot.
- lesenek 3y agoIf the null dereferencing happens in assembly code and not in C, it seems fine to me: the C standard is irrelevant for assembly; after all, it's the C language that introduces UB, not the machine code.