You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.
Even after running the DLL and PDB through ducible, I found that the PDB hashes would differ, so the PE hashes would also differ, leading to cache misses.
Turns out that the linker writes out absolute paths to .obj files in the module info substream!
This is particularly obvious across different developer machines where their usernames are different.
Have you considered adding support to replace those with relative or fake absolute paths?
Do you know if there are any downsides of doing something like that?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is part feature request/part question.
Even after running the DLL and PDB through ducible, I found that the PDB hashes would differ, so the PE hashes would also differ, leading to cache misses.
Turns out that the linker writes out absolute paths to .obj files in the module info substream!
This is particularly obvious across different developer machines where their usernames are different.
Have you considered adding support to replace those with relative or fake absolute paths?
Do you know if there are any downsides of doing something like that?
The text was updated successfully, but these errors were encountered: