Thomas (boggyb) wrote,

Why debugging core/memory dumps on Windows is much more civilised than debugging on Linux

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.
Tags: rant

  • Pancakes!

    Since people have been prodding me for an update, here's a pancake-themed one (as everyone's blogging about pancakes today!). Unlike in the linked…

  • Snap, crackle, pop (again)

    [Adam Savage voice] "Well there's your problem!" So while cooking supper the other day the oven went snap, crackle, and pop, and the magic smoke…

  • Of carpentry and networking

    So, I'm not sure if I've bought a wifi router or a Cylon Raider here... Work colleague: Cylon raider. So say we all. Housegroup friend: Or a…

  • Post a new comment


    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.