Skip to content
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

SIGSEGV when it tries to wait for a futex #451

Closed
techmetx11 opened this issue Aug 20, 2024 · 4 comments
Closed

SIGSEGV when it tries to wait for a futex #451

techmetx11 opened this issue Aug 20, 2024 · 4 comments

Comments

@techmetx11
Copy link

techmetx11 commented Aug 20, 2024

The code segfaults when it tries to wait for a futex (related to Tokio)
More info: iv-org/inv_sig_helper#12
A coredump of the crash and build is provided at iv-org/inv_sig_helper#12 (comment)
From the coredump, the program is shown crashing at these first few locations in the code:

  1. unknown function (0x00007fc5ed1a3719)
  2. https://github.com/Amanieu/parking_lot/blob/master/core/src/thread_parker/linux.rs#L112
  3. https://github.com/Amanieu/parking_lot/blob/master/core/src/thread_parker/linux.rs#L66
  4. https://github.com/Amanieu/parking_lot/blob/master/core/src/parking_lot.rs#L635
  5. https://github.com/Amanieu/parking_lot/blob/master/core/src/parking_lot.rs#L600
@Amanieu
Copy link
Owner

Amanieu commented Aug 25, 2024

Are you sure it's actually crashing in that thread? It seems like this is just the main thread which is blocked waiting on a lock while the crash is happening in another thread.

@techmetx11
Copy link
Author

All the other threads are also blocked waiting for a lock (in the coredump)

@Amanieu
Copy link
Owner

Amanieu commented Aug 25, 2024

All of the threads in that core dump are in system calls, which shouldn't be able to cause a SIGSEGV. It seems the core dump was not taken at the moment the crash happened.

@techmetx11
Copy link
Author

techmetx11 commented Aug 25, 2024

All of the threads in that core dump are in system calls, which shouldn't be able to cause a SIGSEGV. It seems the core dump was not taken at the moment the crash happened.

That's weird, because the kernel makes a core dump after the program crashed (or at least, it should be)

Also, it seems like it crashes due to a malloc header corruption at times, as seen in the linked issue

@techmetx11 techmetx11 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 20, 2024
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

2 participants