-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Tokio 1.36.0, panic SHUTDOWN.unpack(current) == 0 || matches!(tick, Tick :: Clear(_))
when using tokio::net::windows::named_pipe
#6365
Comments
It's not easy to reproduce this panic when I directly run by But when I run through |
SHUTDOWN.unpack(current) == 0 || matches!(tick, Tick :: Clear(_))
when using tokio::net::windows::named_pipe
@Darksonn Hi, I'm sorry to bother you. Is there any progress on this issue? |
I missed due to its similarity to #6066. Sorry about that. Unfortunately, I do not have a windows machine available. Which line is the panic on? Your backtrace says line 19, but that is the |
Thanks for your quick reply. The code seems to panic after destroying |
You can assign it to me @Darksonn |
@fufesou what's the command for this debug run in vscode? I can't reproduce it with |
That hotkey is running a command set up by your debugging configuration. Do you have I'm not that familiar with VSCode, so I'm not sure if extensions usually does it for you. But you should be able to find the exact command ran when you invoke debug for Rust projects in VSC. |
This is my But it's so weird that I cannot reproduce this issue anymore. I've tried 1.37 and 1.36. I can reproduce it every time with {
"version": "0.2.0",
"configurations": [
{
"type": "lldb",
"request": "launch",
"name": "Debug executable 'simple_test'",
"cargo": {
"args": [
"build",
"--bin=simple_test",
"--package=simple_test"
],
"filter": {
"name": "simple_test",
"kind": "bin"
}
},
"args": [],
"cwd": "${workspaceFolder}"
}
]
} |
Thanks! I still can't seem to reproduce the issue for both 1.33 and 1.36 even using lldb. Perhaps there's something else? |
Ok. I close this issue because it cannot be produced anymore. Thank you for your time. |
Description
Version
1.36.0
Platform
64-bit (Windows)
Description
I'm using tokio::net::windows::named_pipe to process ipc.
It was ok for tokio 1.28.
I'm facing panic with tokio 1.33 and 1.36.
Example
I tried this code:
logs
More
I can hardly find a useful example.
The doc here also seems wrong.
Originally posted by @fufesou in #6362
The text was updated successfully, but these errors were encountered: