torkell: (Default)
[personal profile] torkell
Reason #1: I can open a core/memory dump without having the corresponding executable.

Reason #2: I can get a complete library list from a core/memory dump without having the corresponding executable.

Reason #3: I can analyse a core/memory dump that came from a different system with different libraries without having to first get those symbols. In fact, I can analyse a core/memory dump without having to get *any* symbols.

Reason #4: I can specify an actual symbol path, that works, without having exactly match the directory structure on the system the core dump came from

Reason #5: Symbol servers. I don't even have to get the symbols myself - I can just tell Windbg "go grab symbols on-demand from these locations" and it Just Works.

Add all these reasons together, and it means that I can take a memory dump from a Windows 2003 server, open it in Windbg on my Windows XP desktop, and immediately be able to examine it. But I can't take a core dump from a Linux server running some random version and get anything remotely sane out of gdb on my Linux desktop.
This account has disabled anonymous posting.
If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

January 2026

S M T W T F S
     123
45678910
11121314151617
18192021222324
25262728293031

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated May. 8th, 2026 10:36 pm
Powered by Dreamwidth Studios