-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Crash "free(): invalid pointer" in sock.read() in a separate task #3674
Comments
Any update here? This is blocking even the simplest server app. |
Is this on a 32-bit system by chance? uv is completely broken there due to FFI bugs. |
Oh, it's obviously a 64-bit system based on the logs. Hm. |
@ttaubert: It's working on OSX lion for me, and I have heard that it's working on an ubuntu 12.04 x86_64 box. What platform are you running into this on, and is it still occurring on the latest incoming branch? |
Thanks for the quick response, I'm on Ubuntu 12.04 as well. Will try the latest incoming branch and report back. |
The provided test file still crashes for me with the latest incoming. |
So in the middle of trying to reproduce this it suddenly stopped occuring. I have no idea why. Closing for now. |
There's been another report of this error. |
Won't be fixed in 0.6 |
Closing this one as WONTFIX, the underlying APIs here are going to be removed when we shift to the new scheduler (shortly), and we have no reports (yet) of such issues in the new scheduler. Sorry, limited time :( |
Implement LLVM x86 bmi intrinsics This implements the intrinsics for both the bmi1 and bmi2 ISA extensions. All of these intrinsics live inside the same namespace as far as LLVM is concerned, which is why it is arguably better to bundle the implementations of these two extensions.
I compiled a little tcp listener example that spawns tasks per connection. The sock.read() call fails when it receives data - just use telnet to connect, type something and hit enter:
This used to work with Rust 0.3 but crashes now with the following message:
The text was updated successfully, but these errors were encountered: