StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Without knowing how exactly you are compressing and encrypting your binaries, it's hard for me to be very specific.</p> <p>This <a href="http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/05/11/pdb-files-what-every-developer-must-know.aspx" rel="nofollow noreferrer">blog post</a> by John Robbins points out that executable images are associated with their PDBs via a GUID that's embedded in the executable's PE header. You should be able to view it by running DUMPBIN /HEADERS on the executable, and looking for the output of Debug Directories. If your compression and encryption has modified the PE headers such that this information isn't available (or correct), then it would explain why your debugger can't find anything.</p> <p>There are a few approaches that I think that you could take to resolve this issue. To really try to get this to work, you might want to consider using WinDbg instead of the Visual Studio debugger. You'll understand why I am recommending this in a moment...</p> <p>WinDbg provides some options that allow the relaxed loading of symbol files. The idea with this option is that, if the source code hasn't changed but the binaries are from a different build than the PDB, the GUID check can be waived and the mismatched symbol file can be loaded. I don't know how well this will work with your compression and encryption, so YMMV.</p> <p>WinDbg and its accompanying tools can be used to dump the GUID from both the executable and the PDB, but I'm omitting that for now because I am hoping that those steps won't be necessary.</p> <p>After you have opened your minidump in WinDbg, you will need to enter several commands into the command line to get this all to work:</p> <pre><code>.symopt +0x40 !sym noisy ld <exe name> </code></pre> <p>The first command enables the <code>SYMOPT_LOAD_ANYTHING</code> option that skips the GUID check. The <code>!sym</code> command enables verbose output for symbol loading so that you may see more detailed error messages. The <code>ld</code> command directs WinDbg to try to load the symbols for the executable name that you will type in the place of <code><exe name></code>. If you repeat the <code>ld</code> command, WinDbg will indicate if it successfully loaded the symbols the first time.</p> <p>Hopefully this helps -- again, I don't know how well this will work with your compression and encryption, but it's worth trying.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload