X64dbg: Errors caused by pdb file

Created on 28 Dec 2017  路  3Comments  路  Source: x64dbg/x64dbg

os: win 7 x64
x32dbg:snapshot_2017-12-26_13-39

  1. Generate exe with latest version vs2017
  2. drag exe to debug (exe and pdb must be in the same directory)
  3. alt + f2
bug not reproduced
Source
picture stonedreamforest

Most helpful comment

That is a very in-depth description of 'errors', that will help narrow the problem down for sure.

picture learn-more on 28 Dec 2017
😄2

All 3 comments

That is a very in-depth description of 'errors', that will help narrow the problem down for sure.

learn-more picture learn-more on 28 Dec 2017
😄2

2017-12-29_09-10-34
@learn-more

stonedreamforest picture stonedreamforest on 29 Dec 2017

This is just a guess, but this may be caused by the obnoxious /DEBUG:FASTLINK setting which was made the default in VS2017. See https://blogs.msdn.microsoft.com/vcblog/2016/10/05/faster-c-build-cycle-in-vs-15-with-debugfastlink/ for info. To get a non-crippled PDB, you need to either set 'Generate Debug Info' to /DEBUG:FULL or set 'Generate Full Program Database File' to true (they do the exact same thing - brilliant UX design).

I'm pretty sure dbghelp.dll from the newer Windows 10 SDKs will recognise these PDBs (I don't know if it can get useful info from them, but at least it shouldn't crash). The downside is no more XP support.

Mattiwatti picture Mattiwatti on 7 Jan 2018
Was this page helpful?
0 / 5 - 0 ratings

Related issues

arash88 picture arash88  路  4Comments
ViRb3 picture ViRb3  路  6Comments
blaquee picture blaquee  路  3Comments
nickwdev picture nickwdev  路  3Comments
amn picture amn  路  5Comments