All geek questions in one place

Debug symbol issue

I am wondering which symbol file is used when parsing a dump file using Windbg or Visual Studio. Suppose my application uses the utility library and the utility library has an associated private symbol file. When there is a crash dump in my application, I need a utility library symbol to analyze the full call stack. But sometimes build / runtime / debug environments are installed with different versions of the utility library, which (for sure) are different versions of the utility library symbols.

Suppose we have a version (for example, version A) of the utility library (and the associated symbol) for assembling (referencing) my application using another version (for example, version B) of the utilities library (and the associated symbol) at run time, when there is a crash and the use of a different version (for example, version C) of the utility library (and the associated symbol) in Windbg when analyzing the crash dump.

My question is, when a crash escalates at runtime, is a version B character used to create a crash dump (to fill a dump with character information)? But if you use a different version of the C character in the Windbg debugging environment, will there be a problem with incorrect character matching? And what version of the library is used for assembly does not matter? Do I understand correctly?

thanks in advance George

0
source share
2 answers

It looks like you want to use Symbol Server so that WinDBG or VS can output the symbols corresponding to the library building you are debugging. If this is a third-party component and you have personal characters, you can either put them on your own server or see if the third party has a public character server.

Windbg , DLL, , ! sym noisy, . , pdb windbg ( lm v, , )

+3

, , ( , , ). , - , - .

+1

Source: https://habr.com/ru/post/1705710/

More articles:


All Articles