CWE-ou-minkata

813 Commits

81 Branches

23 Tags

172 MiB

Tree: 3d0f01ff03

Commit Graph

Author	SHA1	Message	Date
Adam Johnson	389d3c1802	Fix deadlock if plCrashHandler is not running Only wait for the crash server to do its job if it's attached. Silent failures are evil, but it's better than hanging forever.	13 years ago
Adam Johnson	151657a9f2	Fix zombie plCrashHandler issues Win32 HACK: We wait on both the pfCrashCli handle and the crashed semaphore. This way, we can proceed to exit pfCrashSrv when the client process exits insanely.	13 years ago
Adam Johnson	14279794f7	Implement pfCrashHandler pfCrashHandler includes a client that watches plClient for crashes. When it detects a crash, it lets the plCrashSrv (plCrashHandler.exe) know about it. We then produce a mninidump, then signal the client that it's OK to show a crash dialog. See http://www.nynaeve.net/?p=128 for a good explanation of why I split the crash logic into another process.	13 years ago

Author

SHA1

Message

Date

Adam Johnson

389d3c1802

Fix deadlock if plCrashHandler is not running

Only wait for the crash server to do its job if it's attached. Silent
failures are evil, but it's better than hanging forever.

13 years ago

Adam Johnson

151657a9f2

Fix zombie plCrashHandler issues

Win32 HACK: We wait on both the pfCrashCli handle and the crashed semaphore.
This way, we can proceed to exit pfCrashSrv when the client process exits
insanely.

13 years ago

Adam Johnson

14279794f7

Implement pfCrashHandler

pfCrashHandler includes a client that watches plClient for crashes. When
it detects a crash, it lets the plCrashSrv (plCrashHandler.exe) know about
it. We then produce a mninidump, then signal the client that it's OK to
show a crash dialog. See http://www.nynaeve.net/?p=128 for a good
explanation of why I split the crash logic into another process.

13 years ago

3 Commits (3d0f01ff03ca5034644e375f6a1962315ef7b337)