ni.com is currently undergoing scheduled maintenance.
Some services may be unavailable at this time. Please contact us for help or try again later.
LabVIEW
Time Machine Crashes??? (Bug?)
I just crashed LabVIEW 2012 f1 and looking at the crash report, the modification dates of all files are about 1 month in the future.
(The zip file itself has a modification date of 10/4/2012 11:33AM, which is correct).
Wow, LabVIEW knows you are going to crash your machine in a month and premade the reports for you. Well isn't that nice of them.
@JÞB wrote:
@altenbach wrote:
Psst, but the code is actually controlling my DeLorean. I will definitely leave it in the garage on Nov 4. 😄
Well- its not a bug until we can reproduce it. So how, exactly do you crash LabVIEW? I can't tell from your picture.
The hardest part is reproducing it in the future...
The file dates are independent of the crash. I looked at an earlier crash and it had the same problem with the dates.
In this particular case, I was working on this VI. All I did was change the upper limit of the sliders inside the array to a higher value. Bam!
(I was able to reproduce a second time, but not conistently)
Crash report attached.
Seems to be an old problem....
Looking at a 2011SP1 crash from 6/7/2012 1:24pm shows crash files with a date of 7/7/2012 8:24.
Again 1 Month and 7 hours difference. (The 7 hours could be related to the time zone).
Somebody must have thought that January=0 and applied a correction. 😄 We need to generate a crash on December 1. to see if we get 13/1/2012. 😄
This was reported to R&D (CAR # 377384) for further investigation.
BTW - Nice title, elicited a smile while dealing with a bug report.
Roy 
