debug-symbols

How to know the name and/or path of the debug symbol file which is linked to a binary executable?

老子叫甜甜 提交于 2019-12-12 10:43:44
问题 How to know the name and/or path of the debug symbol file which is linked to a binary executable? Suppose you did like this: objcopy --only-keep-debug foo foo.dbg objcopy --strip-debug foo objcopy --add-gnu-debuglink=foo.dbg foo Now foo.dbg has debug symbols, foo only has the link to foo.dbg that gdb can use. Since gdb can know the symbol file from foo, how can we know same without actually running gdb? I have observed that even if I rename the executable from foo to xyz still gdb loads

Make gdb search for symbol files again

此生再无相见时 提交于 2019-12-12 10:08:49
问题 My distribution (Debian) ships debug files in separate packages. So what happens often is that I run a program in gdb until it crashes, in order to obtain a usable backtrace for a bug report. But bt is rather useless, missing the symbol information – because I did not install the corresponding -dbg package. If I install the package now, is there a way to make gdb search for the symbol files again, without losing my current backtrace? 回答1: There is a trick you can use to make gdb try to read

Visual Studio 2010 takes too long loading symbols, symbol file location cannot be removed

末鹿安然 提交于 2019-12-12 08:19:55
问题 Visual Studio takes a lot of extra time loading symbols for external dlls which I'd rather not load. I have fiddled with my symbol settings in VS2008 and these settings seem to be affecting VS2010 How do I stop it loading 3rd party symbols? I've tried: devenv /resetuserdata Tools > Options > Debugging > Symbols (I can't remove or uncheck the pdb file location of: "Environment Variable: _NT_SYMBOL_PATH") I've cleared the above location like so: set _NT_SYMBOL_PATH= actually this made a huge

How can I know what type of debug info is in an ELF object file?

浪尽此生 提交于 2019-12-12 07:46:40
问题 I have an ELF object file. I want to know which type of debugging info it contains. It was compiled with the Diab compiler (C source) for the PPC architecture. I'm pretty sure it was built with debugging symbols. I have tried extracting the debugging info with dwarfdump but I doesn't work so I guess the debugging information is not of type DWARF. $ dwarfdump file.elf No DWARF information present in file.elf Using objdump to show debugging information comes up empty. $ objdump -g file.elf file

Symbol path for WinDbg

馋奶兔 提交于 2019-12-12 05:18:46
问题 My pc underwent an automatic restart and when I checked event viewer, I found the bug check error. I found the location of the .dmp file created. I then downloaded WinDbg and understand the first thing I have to do is set the symbol path and then open crash dump and select the .dmp file. I found a list of the paths to use at https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/setting-symbol-and-source-paths-in-windbg but whenever I open crash dump and click the file, it gives

Microsoft debug symbol don't work

只谈情不闲聊 提交于 2019-12-12 04:23:36
问题 I try to analyze some memory dump. But I stack on debug symbols of some Microsoft dll ( sechost.dll ). What I do: 1) !sym noisy 2) .symfix 3) .sympath My .sympath is: Symbol search path is: srv* Expanded Symbol search path is: cache*;SRV*http://msdl.microsoft.com/download/symbols 4) analyze -v After it I saw symbols loading. But for some symbols I have ...... SYMSRV: The operation timed out SYMSRV: http://msdl.microsoft.com/download/symbols/sechost.pdb/C4FD72A96E384F62A5F796624D37EAB42

Windows Symbol server

 ̄綄美尐妖づ 提交于 2019-12-12 01:34:35
问题 I want to set up a connection to the Windows Symbol server in Visual Studio. I have the following command: symsrv*symsrv.dll*c:\localcache*http://msdl.microsoft.com/download/symbols What should the c:\localcache part be changed to? 回答1: That setting is only appropriate if you use the environment variable. I'm pretty sure from previous questions that you actually use Visual Studio. The MSDN page is here. Or press F1 when you've got the dialog up. 来源: https://stackoverflow.com/questions/4226012

How do I get the line number and path of a method from a pdb using .Net?

左心房为你撑大大i 提交于 2019-12-11 17:31:47
问题 Given an assembly and its pdb, how do I get the line number and path to a method using .Net? 回答1: You will need to use the DIA SDK. Microsoft does not have a managed interface for it, but using DIA in C# has been asked on StackOverflow before. If you are going to try it out in native first you can get the information in question by getting the IDiaSymbol instance for the PDB in question, this is called the 'global scope'. Once you have that you will call findChildren() passing it the

“__tracepoint_sched_process_fork undefined” when run systemstap script

孤者浪人 提交于 2019-12-11 12:42:45
问题 The error info : WARNING: "__tracepoint_sched_process_fork" [/tmp/stapH5cHsd/stap_958d0ff0e571c9357f1e193511d8baa3_269311.ko] undefined! WARNING: "__tracepoint_sys_exit" [/tmp/stapH5cHsd/stap_958d0ff0e571c9357f1e193511d8baa3_269311.ko] undefined! WARNING: "__tracepoint_sys_enter" [/tmp/stapH5cHsd/stap_958d0ff0e571c9357f1e193511d8baa3_269311.ko] undefined! WARNING: "__tracepoint_sched_process_exec" [/tmp/stapH5cHsd/stap_958d0ff0e571c9357f1e193511d8baa3_269311.ko] undefined! WARNING: "_

In Visual Studio, why can I not debug a referenced class library?

青春壹個敷衍的年華 提交于 2019-12-11 10:09:05
问题 I know this probably sounds easy and that a lot of people have asked the same or similar questions. I have spent many hours on this, and none of the solutions work for me. I have a solution that has two projects: Project 1 is a Windows forms application that depends on Project 2. Project 2 is a class library. I have added a reference to Project 2 in Project 1. I selected Add Reference --> Projects, then checked the box for Project 2. I set Project 1 as the startup project. I have the profile