the core2md step is expected to run while the coredump is being gathered (e.g. a callback from /proc/sys/kernel/core_pattern). there you'd have access to the frozen/crashed process. core2md uses extended process details to fill out the dump (maps/modules/etc...).
we could extend the interface to skip all of this if the process is gone. feel free to send a patch :).
in the meantime, you can probably cheat and use /proc/self, and then be aware that you need to ignore all the process-specific details in the minidump because they'll be for a different process.
-mike