I’m currently working on a CRIU images -> core dump
conversion for CRIT(CRiu Image Tool) and while looking
for some info on manually generating core dump, I’ve found an interesting yet
outdated (OMG last changed in 2007!) project called
google coredumper that allows
generating core dumps whenever you want to, which looks like a cool tool to
have for debugging. CRIU is able to dump processes at any point too, but it is
also providing a lot more info about the process’ state, because it can
literally fully restore it from images, so I thought that coredump users (if
there are any left) could use CRIU for their purposes. Though, CRIU images ->
core dump conversion looks like a complete waste of data, so I have another
idea about somehow integrating CRIU images into gdb so it could ask CRIU to
restore the process with --leave-stopped
flag and then attach to the process
for debugging. It also may be a good thing to be able to save state of the task
that is being debugged by detaching and calling criu dump
.