-
Notifications
You must be signed in to change notification settings - Fork 21
Segmentation Fault when running optimzied #39
Comments
Do you think this is a bug in tokio-timer or a bug in Rust codegen? The only unsafe code is in the mpmc file which I copied from the Rust source and is based on the 1024cores design, which is pretty established. |
I basically think it s a bug of rust codegen but did neither know the right place to post the issue nor ambi entirely sure where the buge comes from since i didn t have a detailed look at the implementation of tokio-timer. |
No, I don't get the segfault. My OS is OS X 10.12.6. Maybe report this on the Rust repo? |
Which toolchain are you using? |
I am also getting this on nightly-x86_64-pc-windows-msvc |
Well, tokio-timer is in the process of being rewritten. So, that should "fix" the problem by virtue of it being new code... |
Thanks for the report! This should (hopefully) be fixed by tokio-rs/tokio#249. |
I encountered a segmentation fault after instatiating the default timer when running a binary using
cargo run --release
Here's a link to a minimal setup where i encounter this error:
https://github.com/joeschman/tokio-timer-segfault
While debugging I found out that optimization error can be avoided when inserting a print-statement after line 248 in the file
tokio-timer/src/wheel.rs
I'm not sure if that helps but I am running macOS 10.13.3.
I hope this bug report helps to fix the bug.
The text was updated successfully, but these errors were encountered: