I would build with pdb-only. You will not be able to attach a debugger to the released product, but if you get a crash dump, you can use Visual Studio or WinDBG to examine the stack traces and memory dumps at the time of the crash. If you go with full rather than pdb-only, you’ll … Read more
Here is the answer, thanks to Hans Passant. Note that this solution raises additional questions. Ensure https://referencesource.microsoft.com/ contains the exact version you’re debugging. How? Reference source specifies “.NET Framework 4.6.2” but a module version is something like: “4.6.1586.0” You may need to uninstall security updates as explained here: How do you enable “Enable .NET Framework … Read more
Debug -> Delete All Breakpoints ( http://darrinbishop.com/blog/2010/06/sharepoint-2010-hangs-after-visual-studio-2010-f5-debugging ) After that you can use them again, but do it once. It will remove some kind of “invalid” breakpoints too and then loading symbols will be fast again. I was chasing this issue for days :(.
I think that the version of libc with debug symbols is in /usr/lib/debug/lib. I tried setting my LD_LIBRARY_PATH variable to have this at the front of the path but that did not seem to make a difference. These are not the droids you are looking for. The libraries in /usr/lib/debug are not real libraries. Rather, … Read more
There are a several things to know when setting up a symbol server and/or symbol network share. WinDbg symbol load order Symbols are searched in the symbol path from the beginning to the end, i.e. in the symbol path C:\a;C:\b, it will first look in C:\a and then in C:\b. While this does not really … Read more
Update 2015-10-22: With the Microsoft patch day (2015-10-13) and KB3088195, symbols are available again. However, symbols for the broken version have not been provided, so below may still be useful. Microsoft has already published “good” symbols for ntdll in the past, containing type information like _TEB or _KPRCB. Starting from mid of July 2015, Microsoft … Read more
ok, with the help of the Windbg Extension PDE.dll from Andrew Richards, I see that your application crashes because of an not handled System.UnauthorizedAccessException. I used !PDE.dpx -dse to shows all Stowed Exceptions (those 0xC000027B exceptions): 0:006> !PDE.dpx -dse Start memory scan : 0x0551fc7c ($csp) End memory scan : 0x05520000 (User Stack Base) 0x0551fc94 : … Read more
I would suggest using gdb as the simplest approach. You can even do it as a one-liner, like: gdb -batch -ex ‘file /bin/ls’ -ex ‘disassemble main’
If you’re running on Linux, use objdump –debugging. There should be an entry for each object file in the library. For object files without debugging symbols, you’ll see something like: objdump –debugging libvoidincr.a In archive libvoidincr.a: voidincr.o: file format elf64-x86-64 If there are debugging symbols, the output will be much more verbose.
I blogged this a long time ago, and I don’t know if it still valid or not, but the code is something like… private void testfile(string file) { if(isAssemblyDebugBuild(file)) { MessageBox.Show(String.Format(“{0} seems to be a debug build”,file)); } else { MessageBox.Show(String.Format(“{0} seems to be a release build”,file)); } } private bool isAssemblyDebugBuild(string filename) { return … Read more