12-30-2014 04:20 AM
Hi,
I know from my late experiance with Visual Studio (which produces *.pdb file) that memory crash dump can be analyzed with WinDbg.
Is there any matching application for *.cdb which is produces by Labwindows/CVI?
or there are any way to see why the crash happened offline? (offline - after the memory had been dumped)
Best Regards,
Uriya.
12-31-2014 12:54 PM
The CDB files require a National Instruments internal tool to decrypt. For local debugging, you would be better off using the ConfigCVILogging.exe application available in <National Instruments>/CVI2013/bin to configure an ASCII file to log messages such as errors and warnings. This tool should allow you to view crash data offline.
12-31-2014 10:22 PM
Thanks for your reply,
I've tried ConfigCVILogging.exe but it didn't shed any light on the crash.
Do you know if there a way getting the internal app that you've mentioned (debug .cdb files) ?
Best Regards,
Uriya.
01-02-2015 11:43 AM
You could try checking "Generate map file" in Build >> Target settings window: this could at least help you pointing out which function the error raised in if the crash generates an error message with a memory location to look for.
01-04-2015 01:35 AM
Thanks for your reply,
I'll try crossing the memory location where the crash happened with 'Generate map file' .
I will post here my result. hope it will be soon 🙂
Uriya