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
I am unable to load the PDB for one of my programs from an internal symbol server. I can't figure out why. But IDiaDataSource::loadDataForExe is failing.
What's weird is that 42A6E6342E735EB74C4C44205044422E1 is the correct hash and Visual Studio is able to correctly load this pdb from my symbol server. I have a tool that runs SymInitialize on a running process and it also able to load the pdb.
I've never used IDiaDataSource before and don't know how it works. Stepping through the callbacks nothing stood out to me. It's ultimately returning E_PDB_NOT_FOUND even though
I also verified that I can download Foo.pdb simply by pasting the full URL in my browser. So it's the right URL. It's the right PDB. But loadDataForExe is failing? That's super super weird.
The text was updated successfully, but these errors were encountered:
I'm not very happy with neither complexity (issues like this) nor the speed of DIA libraries. It's not a tiny amount of work to replace the debug symbol loader but it may happen at some point, can't commit to any timeline though.
I am unable to load the PDB for one of my programs from an internal symbol server. I can't figure out why. But
IDiaDataSource::loadDataForExe
is failing.What's weird is that
42A6E6342E735EB74C4C44205044422E1
is the correct hash and Visual Studio is able to correctly load this pdb from my symbol server. I have a tool that runsSymInitialize
on a running process and it also able to load the pdb.I've never used
IDiaDataSource
before and don't know how it works. Stepping through the callbacks nothing stood out to me. It's ultimately returningE_PDB_NOT_FOUND
even thoughI also verified that I can download
Foo.pdb
simply by pasting the full URL in my browser. So it's the right URL. It's the right PDB. ButloadDataForExe
is failing? That's super super weird.The text was updated successfully, but these errors were encountered: