Skip to content
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

rt: fatal, 'chan->task == task' failed in upcall_del_chan #687

Closed
robarnold opened this issue Jul 14, 2011 · 1 comment
Closed

rt: fatal, 'chan->task == task' failed in upcall_del_chan #687

robarnold opened this issue Jul 14, 2011 · 1 comment

Comments

@robarnold
Copy link
Contributor

Was trying to reproduce my mysterious double-free, found this instead. Single-threaded scheduler.
Testcase: https://gist.github.com/1082006

@ghost ghost assigned eholk Jul 14, 2011
@eholk
Copy link
Contributor

eholk commented Jul 14, 2011

Thanks for catching this!

The problem is that we don't have move semantics working correctly for sends. I'm hoping to get this in there by the end of the week.

@eholk eholk closed this as completed in 4a6ccf3 Jul 22, 2011
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
pdietl pushed a commit to pdietl/rust that referenced this issue Apr 23, 2020
Update async/await keywords to real keywords.
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
I refactored how we codegen panic statements so it now it terminate the
program per its spec. I have also removed the hack we had to try to get
the assert location.

Since we currently do not support stack unwinding, the panic codegen
will always terminate immediately and it will not try to unwind the stack.
I added an option to RMC to force the compiler to use abort as the panic
strategy and a check to rmc codegen that will fail if the user tries to
override that.

Another note is that we currently do not support `#[track_caller]` and I
have not changed that.

This change fixes rust-lang#67, fixes rust-lang#466, fixes rust-lang#543, and fixes rust-lang#636. This
change also mitigates rust-lang#545.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants