-
Notifications
You must be signed in to change notification settings - Fork 508
Add null checks for field load/stores #6399
Comments
Something went wrong when I enabled null checking for field operations. I think its a real issue, but i don't really know whats going on in this stack trace.
|
That looks like a reflection stack trace that I've seen a few times with #5842 . Reflection is not enabled, yet, for wasm. This might just go away when I get #5842 finished. At the moment I'm waiting for emscripten-core/emscripten-fastcomp#238. |
Null dereference in |
You could try building with WASM=0 and posting the js for |
ok, So i did a little bit more digging and this works
but this fails
Nothing looks wrong inside EEType__get_Kind/EEType__get_IsCloned, both seem fine. I cant tell if the issue is the EEType symbol for the array itself or if the failure is inside the CastCache when the types aren't actually compatible. |
Both these tests pass in my local branch where I have reflection enabled. Do you have the changes mentioned here #5842 (comment) from #6467? Looks like this was merged 2 days ago. |
I rebased with what is currently in master but I still get the same stack trace |
Is there a branch to look at? |
Loading or storing a field on a null object should throw a NullReferenceException (or trap). #6383 introduces a pattern for doing null checks that we should be able to use similarly for field operations. The operations that should do checks are:
ImportLoadField
)ImportAddressOfField
)ImportStoreField
)The text was updated successfully, but these errors were encountered: