CR_INST_STORE_ZIP_ARCHIVES and CR_AF_TAKE_ORIGINAL_FILE

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use CR_INST_STORE_ZIP_ARCHIVES and CR_INST_DONT_SEND_REPORT flags;
2. In the crash callback, add a file via crAddFile2() using the 
CR_AF_TAKE_ORIGINAL_FILE flags;
3. Generate a crash report.

What is the expected output? What do you see instead?
The ZIP file has all expected files.

The corresponding crash's directory does *not* contain the file added using the 
CR_AF_TAKE_ORIGINAL_FILE flag.  The crashrpt.xml file *does* however list the 
missing file in the file manifest (FileList tag, FileItem node).

I would expect the crash's directory files to correspond with those in the ZIP 
file, especially given the file manifests are the same.

What version of the product are you using? On what operating system?
CrashRpt 1.2.7.
Microsoft Windows XP Build 2600 Service Pack 3

Please provide any additional information below.

Original issue reported on code.google.com by gmacaus...@gmail.com on 15 Nov 2010 at 4:12

[GoogleCodeExporter]

Original comment by zexspect...@gmail.com on 16 Nov 2010 at 4:37

• Changed state: Accepted

[GoogleCodeExporter]

I extended the documentation of the crAddFile2() function. Now it should be 
more clear what flags should be used in what situation. I hope this is enough. 
I didn't change the code. 

Original comment by zexspect...@gmail.com on 15 Feb 2011 at 3:45

• Changed state: Done

[GoogleCodeExporter]

I see a mention of the CR_INST_SEND_QUEUED_REPORTS flag, but in this instance I 
am using the CR_INST_DONT_SEND_REPORT flag.

For the record, this is my CR_INSTALL_INFO::dwFlags setting:

CR_INST_ALL_EXCEPTION_HANDLERS | CR_INST_DONT_SEND_REPORT | 
CR_INST_STORE_ZIP_ARCHIVES

I understand the queued reports could lead to the file not being in the crash 
folder.  However, it is not clear to me why this should be the case when the 
report is not sent.

Original comment by gmacaus...@gmail.com on 15 Feb 2011 at 4:08