debug-symbols

问题 Within my application, I use the MiniDumpWriteDump function (see dbghelp.dll) to write a crash dump file whenever my application crashes. I also use a symbol server to store all my executables and pdb files, so that whenever a customer sends me a crash-dump file, the debugger automatically picks up the correct version of the executable and the debug information. I also store Windows DLL's (ntdll.dll, kernel32.dll, ...) and their debug information in the symbol server (using SymChk). The debug

问题 I am working on some diagnostic tools to help locate memory issues on an embedded ARM platform. Due to memory constraints, I can't load all symbols for all libraries on the unit itself. What information do I need to save to be able to resolve symbols later on a different machine? The machine where I will resolve the symbols is an x86 machine that has a cross toolchain and gdb with all the symbol packages needed. What would I use to resolve the symbols in a batch from this information I've

问题 While debugging a mixed mode application in VS2010, the breakpoint set on a line of code contained in an unmanaged c++ dll source file (called from a managed c# wrapper class) shows the infamous "The breakpoint will not currently be hit. No symbols have been loaded for this document" info message when hovering the mouse over the breakpoint on the line in question. The breakpoint itself is a red circle with a yellow info triangle instead of the usual solid red orb. Of course, the breakpoint

问题 Is there an easy way to map to LLVM instructions from their associated assembly instructions in the output binary? Given an instruction in an x86 binary, I would like to be able to determine with which LLVM IR instruction it is associated. One possibility would be to compile the binary with debug symbols turned on and then associate the instructions based off of source code line, but that seems like a hack and is prone to having a many-to-many mapping between x86 and LLVM IR when ideally it

问题 Is there an easy way to map to LLVM instructions from their associated assembly instructions in the output binary? Given an instruction in an x86 binary, I would like to be able to determine with which LLVM IR instruction it is associated. One possibility would be to compile the binary with debug symbols turned on and then associate the instructions based off of source code line, but that seems like a hack and is prone to having a many-to-many mapping between x86 and LLVM IR when ideally it

问题 I am trying to debug a dump file for an application that I wrote. I added the following symbols paths to WinDbg I assumed this would download the windows symbols necessary to debug this. I then run the following cammand in WinDbg "!analyze -v" This starts analyzing and then fails because of symbols it cannot find. When I look at C:\MyServerSymbols I see the following I would have expected to see more than just the kernelbase.dll The analyze command is complaining that it cannot find the ntdll

问题 I'm trying to debug a program in Code::Blocks. I followed this guide and this short video as far as I could, but the debugger doesn't stop at breakpoints ... I saw a similar question which remained unsolved (I wasn't sure if I should bump it or open a new one with more details), I do have the "Produce debugging symbols [-g]" flag checked. Optimizations and "Strip all symbols [-s]" are also all disabled. I even tried the flag -ggdb as suggested there, no success either. I'm using TDM-GCC 4.5.2

问题 I'm trying to debug a program in Code::Blocks. I followed this guide and this short video as far as I could, but the debugger doesn't stop at breakpoints ... I saw a similar question which remained unsolved (I wasn't sure if I should bump it or open a new one with more details), I do have the "Produce debugging symbols [-g]" flag checked. Optimizations and "Strip all symbols [-s]" are also all disabled. I even tried the flag -ggdb as suggested there, no success either. I'm using TDM-GCC 4.5.2

问题 I am trying to set up GitLink for our debugging symbols but it complains that 'PdbStr is not found on the computer, please install 'Debugging Tools for Windows' However after installing said debugging tools I simply cannot find PDBStr.exe anywhere. Am I missing something? 回答1: After installing the Debugging Tool from Windows 10 SDK, I see the pdbstr.exe under C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\srcsrv\ (64Bit) and C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\srcsrv

问题 I am trying to set up GitLink for our debugging symbols but it complains that 'PdbStr is not found on the computer, please install 'Debugging Tools for Windows' However after installing said debugging tools I simply cannot find PDBStr.exe anywhere. Am I missing something? 回答1: After installing the Debugging Tool from Windows 10 SDK, I see the pdbstr.exe under C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\srcsrv\ (64Bit) and C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\srcsrv