Symbols (pdb) for native dll are not loaded due to post build step

Posted by sean e on Stack Overflow See other posts from Stack Overflow or by sean e
Published on 2009-05-16T20:19:48Z Indexed on 2010/05/01 23:17 UTC
Read the original article Hit count: 209

Filed under:
|
|
|
|

I have a native release dll that is built with symbols. There is a post build step that modifies the dll. The post build step does some compression and probably appends some data. The pdb file is still valid however neither WinDbg nor Visual Studio 2008 will load the symbols for the dll after the post build step. What bits in either the pdb file or the dll do we need to modify to get either WinDbg or Visual Studio to load the symbols when it loads a dump in which our release dll is referenced?

Is it filesize that matters? A checksum or hash? A timestamp?

Modify the dump? or modify the pdb? modify the dll before it is shipped?

(We know the pdb is valid because we are able to use it to manually get symbol names for addresses in dump callstacks that reference the released dll. It's just a total pain in the *ss do it by hand for every address in a callstack in all the threads.)

© Stack Overflow or respective owner

Related posts about minidump

Related posts about WinDbg