Allow IPC to remain usable after requesting a dump #99
Description
Is your feature request related to a problem? Please describe.
After calling request_dump() on the client object (in my code based on the minidumper example), the client connection becomes unusable (i.e. I can not send additional messages from the same client to the server). This is regardless of the server "continue behavior". I always get a Broken pipe on subsequent attempts to communicate.
This is on Linux. I am not sure whether it is a fundamental limitation of the IPC / minidump approach, an error on my part or a Linux-specific issue - even though I cannot find any specific code in your library that explicitly breaks the client-side connection after a dump request.
Describe the solution you'd like
I would like the IPC channel to stay active and usable. To e.g. request multiple dumps or send messages after the dump. The latter is useful because it allows my client process to attempt some risky recovery of useful information after a crash, being sure that the minidump was already written, then sending additional messages.
Describe alternatives you've considered
My current workaround is to simply create two clients from the same application process. Then I use the first client to request the dump and the second to communicate further. This works but seems a bit hacky.
In any case, thanks a lot for this great set of libraries!