creating a dump file for a managed (.net) application using windbg (or mscordmp)

Question

I'm looking into creating dump files for a managed process.

I know that I can use windbg to create a dump file, but I'm wondering if their are any special flags that I should pass to the ".dump" command, given that it's a managed application instead of a native one.

a related side question: I've heard of a tool called mscordmp.exe (if you google it, you can find mention of it online). Is mscordmp still relevant? I can't find a download point for it anywhere, but I thought it might be better suited for dumping managed memory than windbg.

Answer 1

You should use /ma to create full memory dump. Otherwise sos will complain that managed analysis will be very limited.