Skip to content

rt::io::net::tcp methods may throw SIGABRT #7976

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
jedestep opened this issue Jul 22, 2013 · 3 comments
Closed

rt::io::net::tcp methods may throw SIGABRT #7976

jedestep opened this issue Jul 22, 2013 · 3 comments

Comments

@jedestep
Copy link
Contributor

While migrating my code over to this new TCP library, I discovered it'll throw a SIGABRT whenever attempting to connect to an address. It appears to be coming from any method which can raise a condition (i.e. Listener::bind and TcpStream::connect).

Platform is OSX 10.8 x86_64.

@jedestep
Copy link
Contributor Author

@brson
Copy link
Contributor

brson commented Jul 22, 2013

At a guess, I imagine this is simply due to calls to rtabort! because rt::io requires the new runtime, which is not turned on.

@erickt
Copy link
Contributor

erickt commented Jul 22, 2013

@brson said in IRC that the TCP library depends on the new runtime, which isn't finished yet. This is why you are getting these aborts. If you want to help shake out the bugs in the new runtime, try running your code with RUST_NEWRT=1.

@erickt erickt closed this as completed Jul 22, 2013
flip1995 pushed a commit to flip1995/rust that referenced this issue Feb 24, 2022
…teffen

Improve `redundant_slicing` lint

fixes rust-lang#7972
fixes rust-lang#7257

This can supersede rust-lang#7976

changelog: Fix suggestion for `redundant_slicing` when re-borrowing for a method call
changelog: New lint `deref_as_slicing`
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

3 participants