Skip to content

Calling libc::exit immediately after startup causes assertion failure in rust_initialize_rt_tls_key #9473

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.

Sign up for GitHub

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

Jump to bottom
Closed
brson opened this issue Sep 24, 2013 · 1 comment
Closed

Calling libc::exit immediately after startup causes assertion failure in rust_initialize_rt_tls_key #9473

brson opened this issue Sep 24, 2013 · 1 comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.

Comments

@brson
Copy link
Contributor

brson commented Sep 24, 2013

As in #8870. To fix that we stopped calling exit, but there's a deeper problem that might be fixable.
brson added a commit to brson/rust that referenced this issue Sep 24, 2013
@brson
Don't use libc::exit. rust-lang#9473
6d03897 
This can cause unexpected errors in the runtime when done while
scheduler threads are still initializing. Required some restructuring
of the main_args functions in our libraries.
@alexcrichton alexcrichton mentioned this issue Sep 26, 2013
Closed
@huonw
Copy link
Member

huonw commented Mar 2, 2014

The following runs fine on Linux, but, I don't recall ever being able to reproduce #8870 on this computer.

fn main() {
    println!("hi");
    unsafe { std::libc::exit(0) }
}

It seems unlikely that we ever accidentally fixed the fundamental problem, but rust_initialize_rt_tls_key disappeared in e8bf078, so I'm closing this.

@huonw huonw closed this as completed Mar 2, 2014
flip1995 pushed a commit to flip1995/rust that referenced this issue Mar 7, 2024
@GuillaumeGomez
Add regression test for rust-lang#9473
bd9b9ff
flip1995 pushed a commit to flip1995/rust that referenced this issue Mar 7, 2024
@bors
Auto merge of rust-lang#12423 - GuillaumeGomez:code-wrapped-element, …
21efd39 
…r=Alexendoo

Don't emit "missing backticks" lint if the element is wrapped in `<code>` HTML tags

Fixes rust-lang#9473.

changelog: Don't emit "missing backticks" lint if the element is wrapped in `<code>` HTML tags
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brson @huonw