News for hackers. Stuff that matters.
Re:The Emacs dumper dispute by sedachv on Thursday December 01, 2016 @01:35PM (#13082042)
> 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?

Re:The Emacs dumper dispute by int_19h on Thursday December 01, 2016 @03:09PM (#13083018)
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.
Re:The Emacs dumper dispute by sedachv on Thursday December 01, 2016 @05:34PM (#13084205)
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.

Re:The Emacs dumper dispute by int_19h on Thursday December 01, 2016 @06:27PM (#13084600)
Are all heap-related structures be stored in kernel memory, though? There's nothing in userspace for bookkeeping?
Re:The Emacs dumper dispute by sedachv on Thursday December 01, 2016 @08:26PM (#13085219)
The kernel just gives you pointers and sizes via mmap/sbrk, it is up to you to keep track of them.