You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chingjun opened this issue
Aug 7, 2020
· 2 comments
Assignees
Labels
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.crashProcess exits with SIGSEGV, SIGABRT, etc. An unhandled exception is not a crash.
The text was updated successfully, but these errors were encountered:
a-siva
added
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
crash
Process exits with SIGSEGV, SIGABRT, etc. An unhandled exception is not a crash.
labels
Aug 8, 2020
I have posted the instructions to reproduce in the internal link.
no-responsebot
removed
the
needs-info
We need additional information from the issue author (auto-closed after 14 days if no response)
label
Aug 8, 2020
The VM assumes parents appear before children when iterating loading units in id order. Normally this happens as a side-effect of sources being loaded in import order, but this might not happen in environments that combine separately produced kernel files.
Bug: #42985
Change-Id: Ice9e2e07cf2aa89e91ab313951cc33c1924f17ed
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/158066
Commit-Queue: Ryan Macnak <rmacnak@google.com>
Reviewed-by: Alexander Markov <alexmarkov@google.com>
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.crashProcess exits with SIGSEGV, SIGABRT, etc. An unhandled exception is not a crash.
Stack trace during crash:
Context: cl/323858212
cc @rmacnak-google
Thanks.
The text was updated successfully, but these errors were encountered: