-
Notifications
You must be signed in to change notification settings - Fork 103
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
Pdb still locks #12
Comments
I have found the problem. before cr_plugin_load, I had to load and unload the dll to execute a function. but visual studio didn't seem to unlock the pdb. sorry to bother you and thanks for the great lib |
Thanks for the link, that is interesting and remembers me that I have some more things to write in the troubleshooting section, I'll take the time and add this info there too. |
same problem as fungos#12 the original pdb is locked for some reason if the pdb-string is garbled, as it was without a terminating zero. original path: "d:\\dev\\netphys\\_build_win_d\\game\\game.pdb" patched: "gam0.pdbetphys\\_build_win_d\\game\\game.pdb" after bugfix: "gam0.pdb\0etphys\\_build_win_d\\game\\game.pdb"
Add option to not check for library changes. * tidy up + fix variable shadow warning Fix the documentation Add braces to the condition Rename check to reloadCheck update README.md fix variable shadow warning, -we4456 declaration of 'x' hides previous local declaration. on msvc * fix outdated docs i dont understand git :-) * fix initial dll lock in visual studio 2017 same problem as #12 the original pdb is locked for some reason if the pdb-string is garbled, as it was without a terminating zero. original path: "d:\\dev\\netphys\\_build_win_d\\game\\game.pdb" patched: "gam0.pdbetphys\\_build_win_d\\game\\game.pdb" after bugfix: "gam0.pdb\0etphys\\_build_win_d\\game\\game.pdb"
Hi,
I was testing out your library and noticed that on visual studio 2015 (update 3) it still locks the original pdb.
I have checked cr_pdb_replace function to see if the pdb name is replaced and it does, but after cr_so_load, the original pdb is locked instead of versioned one.
does visual studio gets it's pdb path from somewhere else instead of binary ?
The text was updated successfully, but these errors were encountered: