Why? A binary executable does not rely on the very fine details of the implementation of the OS heap manager, for example, while a dump necessarily would.
> A binary executable does not rely on the very fine details of the implementation of the OS heap manager, for example, while a dump necessarily would.
What are you talking about? What is it about brk(2)/sbrk(2)/mmap(2) that would be a problem?
Correct me if I'm wrong, but if you make a process dump of the entire process, that dump would include internal structures used to maintain its heap, no? If those structures change between OS versions, for example, then the process dump from an older version would represent corrupted heap when loaded on a newer version.
None of the kernel data structures are saved or even visible to the process - the kernel memory (on Linux x64 everything mapped in the upper 128TiB) is not readable by the process.
You can have a problem if the kernel system call interface changes, but that is a problem for every executable. You would need to re-compile everything on the system.
Are all heap-related structures be stored in kernel memory, though? There's nothing in userspace for bookkeeping?
This argument makes about as much sense for core files as it does for binary executables, which is to say, not very much.