Support multiple crash reports per application instance

[GoogleCodeExporter]

Similar to Issue 125.

An error report is uniquely identified using the error report GUID. The GUID is 
generated at the start of the application. When generating error reports 
multiple times without closing the application, all the error reports are 
identified with the same GUID, which leads to following problems:

1) If the previous CrashSender is still running, another CrashSender will not 
be able to write into the same directory.
2) When postponing sending of the reports, the last report overwrites the first 
one.
3) Problem at the processing side, when extracting multiple archives with the 
same file name and ID.

It would solve the problem, if the application instance GUID was extended with 
a crash serial number.

Thanks, Vojtech

Original issue reported on code.google.com by bubn...@gmail.com on 3 Jan 2012 at 1:11

[GoogleCodeExporter]

Original comment by zexspect...@gmail.com on 5 Jan 2012 at 8:32

• Changed state: Accepted
• Added labels: Component-Logic

[GoogleCodeExporter]

Now it regenerates new GUID insided of CCrashHandler::GenerateErrorReport() 
method.

Original comment by zexspect...@gmail.com on 25 Aug 2012 at 8:31

• Changed state: Fixed

[GoogleCodeExporter]

This issue was closed by revision r1341.

Original comment by zexspect...@gmail.com on 25 Aug 2012 at 8:32