debug-symbols

How can I check on debug symbol status with Eclipse?

只愿长相守 提交于 2019-11-28 11:23:40
While discussing another question I asked, @Aaron Digulla pointed out the following: If you installed the Java SDK, there should be a "src.zip" file in the root directory of the Java installation. If it's missing, download Java again. Eclipse should find the source automatically and show it to you when you open the type JTable (or when you click on the line in the stack trace). The file src.zip is present for me, but I still can't access the source of JTable like @Aaron said. What could be the problem? How can I solve this with Eclipse? The "Unknown Source" worries me, though. it means your

Using nuget & Symbols servers

元气小坏坏 提交于 2019-11-28 10:57:06
I must be doing it wrong. I am using VS2012, c#. I am using nuget to manage my packages. Previously I always created an 'External References' directory and managed packages myself. I decided to now follow the new way of package management. Anyway, nuget is working a treat. I have it setup so that packages are not included in svn (code repository) and that missing packages get downloaded if required. All works, for all developers on my team and also on our Team City box. Problem comes when I want to debug one of these packages (ie step into the package source). I have setup VS2012 for symbol

Serialize execution of symstore via Powershell or BATCH

大城市里の小女人 提交于 2019-11-28 10:31:34
We are working to integrate a step into our continuous integration (CI) server (CruiseControl.NET). We want to register the debug symbols *.pdb generated from our build process into a Microsoft Symbol Server. As implemented by Microsoft, a symbol server is a directory structure Visual Studio uses to find the *.pdb debug symbols for C++/C# executables. Microsoft provides a command symstore that takes debug symbols in one directory and populates the central symbol store directory as appropriate. The trouble is symstore explicitly states it is not safe to run concurrently. What approaches or

How to get a Windows symbol server set up

限于喜欢 提交于 2019-11-28 09:20:41
I have a spare server on the network that I'd like to have host all of our build symbols. I already know how to set up a symbol cache on my local development system and pointing my debugger (e.g. Windbg) to that path in 'Symbol File Path'. I presumed that I could do the same with another system on the network that has its own symbol cache (e.g. \\host\symbols). I set up the server and enabled file sharing on the directory, so I'm able to access it remotely through Windows Explorer. However, when I try pointing to it in WinDbg, it doesn't seem to pick up the symbols there. The Symbol File Path

Getting the original variable name for an LLVM Value

半腔热情 提交于 2019-11-28 04:45:22
The operands for an llvm::User (e.g. instruction) are llvm::Value s. After the mem2reg pass, variables are in SSA form , and their names as corresponding to the original source code are lost. Value::getName() is only set for some things; for most variables, which are intermediaries, its not set. The instnamer pass can be run to give all the variables names like tmp1 and tmp2 , but this doesn't capture where they originally come from. Here's some LLVM IR beside the original C code: I am building a simple html page to visualise and debug some optimisations I am working on, and I want to show the

What's the risk of deploying debug symbols (pdb file) in a production environment?

旧城冷巷雨未停 提交于 2019-11-28 02:53:39
I have an application that logs exception strack traces and I wanted those stack traces to include file names and line numbers when deployed in production. I figured out how to deploy the debug symbols w/ the assembly, but in the process of researching the issue I ran accross this question , which implies that it's not a good idea to include pdb files in a production environment. A comment to the accepted answer says "...debugging information can give away sensitive data and be an attack vector. Depending on what your app is." So what sort of sensitive data might be exposed? How can debug

Why does a 2-stage command-line build with clang not generate a dSYM directory?

微笑、不失礼 提交于 2019-11-27 23:25:43
问题 I have a simple project I want to debug want to produce dSYM folder with debugging symbols. Running: clang++ -std=c++14 -stdlib=libc++ -g -o Lazy Lazy.cpp Creates Lazy.dSYM as I expect. However: clang++ -std=c++14 -stdlib=libc++ -g -c Lazy.cpp clang++ -stdlib=libc++ -g -o Lazy Lazy.o Does not create Lazy.dSYM (It seems that the symbols are embedded in the binary). Sadly the 2-step build is what my modified makefile does. How can I generate Lazy.dSYM from a 2-stage compile-and-link build? I

Getting rid of “There is no source code available for the current location.”

独自空忆成欢 提交于 2019-11-27 19:37:10
OK, this is my own fault, but I can't seem to rescue myself. Whenever I try to step into a class that has fields with assignments calling into .NET code, I get a dialog box that contains the text "There is no source code available for the current location.": For instance, stepping into the constructor of the following class would give me the above message: public class Test { private Stack<String> _Dummy = new Stack<String>(); public Test() { } } I assume this is because at some point I fiddled with the settings for the symbol server, but no matter what I fiddle with now, I can't seem to get

gcc : Is using -Werror and -pedantic considered good practice?

﹥>﹥吖頭↗ 提交于 2019-11-27 15:54:00
问题 I'm just digging into the gcc manual and some things are still unclear to me: When specifying a std, should I always use -pedantic in conjunction? When using -g, it the standard level sufficient or should I specify level 3, i.e. -g3? Is it good practice to use -Werror to promote all warnings to errors and -pedantic-errors to promote all pedantic warnings to errors? 回答1: If you are writing a library, please do make sure that a simple program like #include <yourlib.h> int main() { return 0; }

Make gcc put relative filenames in debug information

瘦欲@ 提交于 2019-11-27 14:47:41
问题 The project I'm compiling uses CMake, which loves absolute pathnames. When I compile with debugging information enabled, gcc puts those long names into .debug_str sections, which is bad for debugging. I'd like to have short relative-to-project-root pathnames there instead. Is there some option to tell gcc to strip some part of pathname before emitting debug data? Or, maybe, there is some tool that could do that on compiled binaries? I've tried using SET(CMAKE_USE_RELATIVE_PATHS ON) (which