Skip to content

runtime/vm/flow_graph_allocator.cc:1301: error: unreachable code #22693

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DartBot opened this issue Mar 6, 2015 · 4 comments
Closed

runtime/vm/flow_graph_allocator.cc:1301: error: unreachable code #22693

DartBot opened this issue Mar 6, 2015 · 4 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.

Comments

@DartBot
Copy link

DartBot commented Mar 6, 2015

This issue was originally filed by [email protected]


runtime/vm/flow_graph_allocator.cc:1301: error: unreachable code

No other stacktrace, can't find the reason why server VM dies.

version 1.8.5
ubuntu server 14.04 64bit

@DartBot
Copy link
Author

DartBot commented Mar 6, 2015

This comment was originally written by [email protected]


There was no problem in previous version

@lrhn
Copy link
Member

lrhn commented Mar 6, 2015

Can you show the code that triggered the error?


Added Area-VM, Triaged labels.

@mraleph
Copy link
Member

mraleph commented Mar 6, 2015

I manually went through instruction templates and found that BinaryUint32Op with * has a wrong Location summary.

I will fix this and see that we make this code more robust.


Set owner to @mraleph.
Added Accepted label.

@mraleph
Copy link
Member

mraleph commented Mar 6, 2015

I think this should be fixed by r44296.

Thanks for the report!


Added Fixed label.

@DartBot DartBot added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. labels Mar 6, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
Projects
None yet
Development

No branches or pull requests

4 participants