breakpad/src/client/windows/crash_generation
doshimun 0ded3d718f Add a way for the client apps to specify custom information in case of out-of-process
scenarios that the OOP server can use in whatever way it wants to.

Fix a bug in CrashGenerationserver where CreateNamedPipe failure was not checked correctly.

TODO in near future: Add a custom stream to minidump files for the custom information.



git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@267 4c0a9323-5329-0410-9bdc-e9ce6186880e
2008-05-05 20:03:56 +00:00
..
client_info.cc Add a way for the client apps to specify custom information in case of out-of-process 2008-05-05 20:03:56 +00:00
client_info.h Add a way for the client apps to specify custom information in case of out-of-process 2008-05-05 20:03:56 +00:00
crash_generation.vcproj Fix newlines (#253). rs=ted.mielczarek 2008-04-07 21:50:57 +00:00
crash_generation_client.cc Add a way for the client apps to specify custom information in case of out-of-process 2008-05-05 20:03:56 +00:00
crash_generation_client.h Add a way for the client apps to specify custom information in case of out-of-process 2008-05-05 20:03:56 +00:00
crash_generation_server.cc Add a way for the client apps to specify custom information in case of out-of-process 2008-05-05 20:03:56 +00:00
crash_generation_server.h Add one more parameter to the ClientDumpRequestCallback in crash generation server 2008-04-17 21:21:48 +00:00
minidump_generator.cc Add one more parameter to the ClientDumpRequestCallback in crash generation server 2008-04-17 21:21:48 +00:00
minidump_generator.h Add one more parameter to the ClientDumpRequestCallback in crash generation server 2008-04-17 21:21:48 +00:00
ReadMe.txt Fix newlines (#253). rs=ted.mielczarek 2008-04-07 21:50:57 +00:00

=========================================================================
 State machine transitions for the Crash Generation Server
=========================================================================

=========================================================================
               |
 STATE         | ACTIONS
               |
=========================================================================
 ERROR         | Clean up resources used to serve clients.
               | Always remain in ERROR state.
-------------------------------------------------------------------------
 INITIAL       | Connect to the pipe asynchronously.
               | If connection is successfully queued up asynchronously,
               | go into CONNECTING state.
               | If connection is done synchronously, go into CONNECTED
               | state.
               | For any unexpected problems, go into ERROR state.
-------------------------------------------------------------------------
 CONNECTING    | Get the result of async connection request.
               | If I/O is still incomplete, remain in the CONNECTING
               | state.
               | If connection is complete, go into CONNECTED state.
               | For any unexpected problems, go into DISCONNECTING state.
-------------------------------------------------------------------------
 CONNECTED     | Read from the pipe asynchronously.
               | If read request is successfully queued up asynchronously,
               | go into READING state.
               | For any unexpected problems, go into DISCONNECTING state.
-------------------------------------------------------------------------
 READING       | Get the result of async read request.
               | If read is done, go into READ_DONE state.
               | For any unexpected problems, go into DISCONNECTING state.
-------------------------------------------------------------------------
 READ_DONE     | Register the client, prepare the reply and write the
               | reply to the pipe asynchronously.
               | If write request is successfully queued up asynchronously,
               | go into WRITING state.
               | For any unexpected problems, go into DISCONNECTING state.
-------------------------------------------------------------------------
 WRITING       | Get the result of the async write request.
               | If write is done, go into WRITE_DONE state.
               | For any unexpected problems, go into DISCONNECTING state.
-------------------------------------------------------------------------
 WRITE_DONE    | Read from the pipe asynchronously (for an ACK).
               | If read request is successfully queued up asynchonously,
               | go into READING_ACK state.
               | For any unexpected problems, go into DISCONNECTING state.
-------------------------------------------------------------------------
 READING_ACK   | Get the result of the async read request.
               | If read is done, perform action for successful client
               | connection.
               | Go into DISCONNECTING state.
-------------------------------------------------------------------------
 DISCONNECTING | Disconnect from the pipe, reset the event and go into
               | INITIAL state and signal the event again. If anything
               | fails, go into ERROR state.
=========================================================================