-
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
runtime segfaults (stack overflow) at exit when logging is on #2726
Comments
@bblum What OS was this on? I haven't seen it. I know this is old, but if you wouldn't mind trying to reproduce it with a recent revision, that would be great. |
It was on linux. I can't remember if I was doing anything specific (almost certainly using multiple tasks, though) before it segfaulted. It happened pretty frequently. |
This still happens on Linux (x86_64) but not OS X 10.8.2. Tried with: fn main() {
core::io::println("Hello world!");
}
|
This should be easy to fix. This is called from |
the sched reaper will not exist in the new scheduler |
Oldsched is dead; long live newsched. |
add provenance-related test One of the cases in rust-lang/miri#2182 actually works as intended since rust-lang#104054 (or maybe even earlier); make sure we test that.
add provenance-related test One of the cases in rust-lang/miri#2182 actually works as intended since rust-lang#104054 (or maybe even earlier); make sure we test that.
With RUST_LOG=::rt, the runtime segfaults near the very end of its exit path.
The call is "KLOG_("Deleting scheduler %d", id);" in rust_scheduler::wait_for_schedulers. It gets into buffered_vfprintf and attempts to use 8K of stack space, which is apparently too far.
The text was updated successfully, but these errors were encountered: