This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 238
Occasional segfault with --threads #60
Comments
eklitzke
changed the title
Occassional segfault with --threads
Occasional segfault with --threads
Mar 9, 2017
I have a bunch of these core dumps, and they're always at this offset in this function. Here's another example with a slightly different disassembly:
In this case the pyflame process hit an assertion error which caused it to bail out, I believe before restoring the original code value. |
I think I understand what is happening now. When I pyflame the target process, that process could already be blocked in a syscall. In this case, the syscall is |
I released v1.3.1, which mitigates this when |
This was fixed by #61 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am sometimes getting segfaults when using
--threads
. Here's some info from a core dump:What's suspicious here is that
%rip
is at 0x7f3ef11af959, which is not a valid address. In fact, it's two bytes past a valid address. The syscall instruction is two bytes. So it looks to me like there is an issue where the instruction pointer isn't being restored properly.The text was updated successfully, but these errors were encountered: