> but we probably want to investigate why this is happening in this mode at some point (maybe we make assumptions about not using this compilation method).
We do indeed assume a heap of 4GB, so the crash, SIGILL etc. are all completely expected.
Bug 1607278 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> but we probably want to investigate why this is happening in this mode at some point (maybe we make assumptions about not using this compilation method). We do indeed assume a heap of 4GB, so the crash is completely expected. > The crash is due to a failed bounds check (which compiles to ud2). I think this is the right behavior Yup!
> but we probably want to investigate why this is happening in this mode at some point (maybe we make assumptions about not using this compilation method). We do indeed assume a heap of 4GB, so the crash is completely expected. >> That crash says it's due to SIGILL; > The crash is due to a failed bounds check (which compiles to ud2). I think this is the right behavior Yup!