CR_INST_DONT_SEND_REPORT Issue

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Using statically linked LIB (dll not tested)
2. Set pCrash_info->dwFlags = CR_INST_DONT_SEND_REPORT | CR_INST_APP_RESTART
3. Set a custom directory for files
4. Crash the app

What is the expected output? What do you see instead?
I suppose I can find a ZIP file equal to the one sended via email, instead the 
directory is created ( specified + MD5 hash) but it contains only XML and dump 
file, no screenshot or attached files

What version of the product are you using? On what operating system?
1.26.804 - VS2008 SP1 - Vista 32 SP1

Please provide any additional information below.

Original issue reported on code.google.com by zacca...@zaksoft.com on 15 Sep 2010 at 2:03

[GoogleCodeExporter]

1. Files are stored in uncompressed state. This is by design. It is to simplify 
the work of CrashSender.exe when it enumerates and sends queued error reports 
(it's easier to enumerate uncompressed files than to enumerate ZIP archives and 
uncompress each one).

2.Did you use crAddScreenshot() to attach a screenshot? If not, the screenshot 
will not be generated. The same is true for crAddFile() and attached files. By 
default error report contains XML and DMP file only.

Original comment by zexspect...@gmail.com on 16 Sep 2010 at 5:15

[GoogleCodeExporter]

Ok, I undertstand that this is by design, but can you add in future release a 
flag that do not delete zip file (sended, aborted, cancelled) so that they can 
etrieved again wheen needed ?

TIA.

Original comment by zacca...@zaksoft.com on 16 Sep 2010 at 5:23

[GoogleCodeExporter]

In this case screenshot was not added, but there are 4 files, and these are not 
present (probably you take them from source directories when zipping), but 
doing that way you cannot be sure that failes are unchanged when you collet 
them manually from (shared in my case) directories. I think if 
CR_INST_DONT_SEND_REPORT is used you have to copy all files specified with 
crAddFile into crash directyory

Original comment by zacca...@zaksoft.com on 16 Sep 2010 at 5:27

[GoogleCodeExporter]

Ok, I will add the CR_INST_STORE_ZIP_ARCHIVES flag that would allow to store 
archived error reports as ZIP files, but uncompressed error report files will 
be stored, too.

The crAddFile2() function's CR_AF_MAKE_FILE_COPY flag allows to make a copy of 
the file and store it in the error report folder. Doesn't this work for you? 

I'm not sure I should copy all files to error report folder in case of 
CR_INST_DONT_SEND_REPORT. It would be better if you use crAddFile2() with 
CR_AF_MAKE_FILE_COPY flag.

Original comment by zexspect...@gmail.com on 16 Sep 2010 at 5:49

• Changed state: Accepted

[GoogleCodeExporter]

The CR_INST_STORE_ZIP_ARCHIVES flag is introduced in v.1.2.7

Original comment by zexspect...@gmail.com on 10 Oct 2010 at 2:37

[GoogleCodeExporter]

Original comment by zexspect...@gmail.com on 10 Oct 2010 at 2:37

• Changed state: Fixed