Think about the following scenario: An application developer figured out the library he is in use crashes. So he created a test project to isolate this problem, and have it sent to the library developer.
However the feedback of the library developer is that they cannot reproduce the problem. So the application developer used the same test project in different computers and have the same result. Finally, he run a stand alone VirtualBox machine with minimum software installed, and catches a crash.
What he wanted to do is to let the library developer have a look at this and confirm the issue. Just telling them “something gone wrong” means nothing, you have to give them the whole crime scene. So the best way is to take a snapshot of the running machine (with the crash dialog still open), and let the library developer to access this and (probably) work on it.
However, there are difficulties to do so in VirtualBox. Here is some attempts:
Export and import appliance is just creating snapshot of hard drive, not the memory.
I can copy all
.vdifile across, and have the target machine set everything up. However, when I tried to bring the saved state it says it is invalid (
VERR_SSM_INTEGRITY_FOOTER). (I tried to preserve the machine UUID but this does not help)