We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have no guarantee that the threads context are stored at an aligned offsets in the dmp file, as a result those are UBs:
I've seen this leads to crashes in an application using udmp-parser-rs when the compiler reads from the context using SSEs instructions:
udmp-parser-rs
(4ed8.2b6c): Access violation - code c0000005 (!!! second chance !!!) p2o_miami22_finders!ZN5rp_bf7explore17h9ea7b88746d86be0E+0x580: 00007ff6`a65a5a60 440f28b880000000 movaps xmm15,xmmword ptr [rax+80h] ds:0000019e`3c1985a8=00000000000000000000000019720330
The text was updated successfully, but these errors were encountered:
Fix #2 by reading a copy of the thread contexts using read_unaligned.
read_unaligned
ca35be0
Fix UB when reading / copying thread's contexts using read_unaligned (
bc194cf
#2) (#3)
Successfully merging a pull request may close this issue.
We have no guarantee that the threads context are stored at an aligned offsets in the dmp file, as a result those are UBs:
I've seen this leads to crashes in an application using
udmp-parser-rs
when the compiler reads from the context using SSEs instructions:The text was updated successfully, but these errors were encountered: