Rainer Schuetze

What's your command line for keeping debug symbols in a separate file? I haven't found anything appropriate with --help. If you want to ship an executable with stripped debug info,...

Sorry for the late reply, it somehow slipped through the cracks. A crucial part of the work is done by a Microsoft library (mspdb*.dll), i.e. generating the PDB file from...

You can use the 32-bit version to convert 64-bit executables, there's just a lower limit on the maximum size (about 1GB IIRC).

Indeed, `_fstat64` could be used instead, but I suspect that won't be the only place where assumptions will break. PR welcome ;-)

The best information available I know of is in these files: https://github.com/microsoft/microsoft-pdb/tree/master/include (these were not available at the time this program was written). LLVM also has tools to generate CodeView...

I suspect that your code for functiion_a/b/c is inlined, so there are no stack frames to follow. Maybe using `-fno-inline` while keeping the rest of the optimizations helps.

Indeed, the INSTALL document is pretty much outdated. These days, cv2pdb is not necessary to debug D code in Visual Studio anymore. With dmd, compile to COFF with `-m64` or...

You should use cv2pdb_vs12.sln. cv2pdb.sln is for VS2008. The makefile contains target cv2pdb_exe that uses the newer solution. I guess I should remove the ancient cruft.

> How do I do that? I am using the WinDbg that is included in WDK 7.1.0. No idea if there is something special about that version, but AFAICT any...

Are you able to set breakpoints? You can use https://github.com/Microsoft/microsoft-pdb/tree/master/cvdump to dump the resulting PDB file and verify whether it contains sensible line numbers.