Date time on zip file

[GoogleCodeExporter]

What steps will reproduce the problem?
Just send a crash report ( tested Win XP SP3 / Vista SP2 - both Italian)

What is the expected output? What do you see instead?
DateTimes for files generated by CrashSender ( .dmp, .png, .xml ) are 
wrong, the same with files copied into report using crAddFile()

What version of the product are you using? On what operating system?
latest (problem was present also in previous versions) 1.24

Please provide any additional information below.
for example a zip file dated 5-22-2010 11:39 have inside files dated 6-22-
2010 09:39. Each files is saved with 1 month added and (i think) in GMT 
and not local time ( i suppose this: Italy is -1 TZ and with daylight 
saving active )

Original issue reported on code.google.com by zacca...@zaksoft.com on 27 May 2010 at 6:25

[GoogleCodeExporter]

Actually zip timestamps are not intended to use by somebody. Instead you can 
use the
SystemTimeUTC tag in crashrpt.xml file.

I'll try to fix this anyway. 

Original comment by zexspect...@gmail.com on 27 May 2010 at 12:11

• Changed state: Accepted

[GoogleCodeExporter]

I fixed the incorrect month number (tm_zip.tm_mon required month number to be 
zero-based, not 1-based).

Do you think file timestamps should be in local time, not in GMT? Would this be 
convenient for server-side error report analysis? 

Original comment by zexspect...@gmail.com on 16 Jun 2010 at 2:42

[GoogleCodeExporter]

yes (in my opinion). Since mail can arrive much later (or crash report can be 
re-sended) it's a way to get immediately time of crash.

People that make analisys of crashed and want to use TMZ can look at 
SystemTimeUTC in XML

Original comment by zacca...@zaksoft.com on 18 Jun 2010 at 4:51

[GoogleCodeExporter]

Fixed in v.1.2.5.

Original comment by zexspect...@gmail.com on 26 Jun 2010 at 12:24

• Changed state: Fixed