Loading symbols from an incremental PDB

Question

Loading symbols from an incremental PDB

Yogurt4 opened this issue 6 years ago · comments

Hi,

When you have incremental linking enabled (/INCREMENTAL) and maybe /DEBUG:FASTLINK, VerySleepy cannot load the symbols at all, so only function addresses are displayed. Could there be an improvement for this?

Sometimes it's just necessary to profile a debug build, and incremental linking saves a lot of compilation/linking time.

Vladimir Panteleev · Answer 1 · Wed Jun 27 2018 14:05:18 GMT+0800 (China Standard Time)

Probably, you just need a newer version of dbghelp.dll ?

Try replacing dbghelpms.dll with the latest one you have available (probably the one that came with the toolchain you used to create the PDB in question).

Yogurt4 · Answer 2 · Wed Jun 27 2018 15:18:03 GMT+0800 (China Standard Time)

Thank you, this really works.
It only took a while to get the proper versions. My VS 2017 has 10 instances of dbghelp.dll scattered around in various subdirectories.

vegorovinno · Answer 3 · Wed Mar 13 2019 18:28:32 GMT+0800 (China Standard Time)

Thank you, this really works.
It only took a while to get the proper versions. My VS 2017 has 10 instances of dbghelp.dll scattered around in various subdirectories.

Can you tell which version works best?

I've tried placing various versions and Very Sleepy behavior ranges from 'hangs irrecoverably' to 'too slow to start profiling' (thread list update takes 4 seconds so clicks on Profile Selected are just ignored.

vegorovinno · Answer 4 · Thu Mar 14 2019 20:42:33 GMT+0800 (China Standard Time)

Best version for me turned up in $:\Windows\System32\dbghelp.dll - no hangs and no missing symbols.

Vladimir Panteleev · Answer 5 · Thu Aug 19 2021 18:32:05 GMT+0800 (China Standard Time)

Could you please see if this issue occurs with the latest release:
https://github.com/VerySleepy/verysleepy/releases

I believe someone contributed a fix (version bump of DbgHelp) which may address this particular problem. If you encounter further problems, please leave a comment or open a new issue. Thanks!