Jump to content
News about the LabVIEW Wiki! Read more... ×
Sign in to follow this  
ThomasGutzler

Debugging my executable crashes LabVIEW

Recommended Posts

I built my executable with Debug and "Wait for debugger on launch" enabled.
When I run it and attach with LabVIEW, it downloads the vis and then crashes LV. The application remains open and not running. I never get to see the local debug version of the application in LV. If I open the source it runs without problems. The executable runs too, but only if there is LabVIEW installed on the machine - that's why I started debugging it. See crash log below, which I'm not sure how to interpret. The two vis mentioned in there are not broken in the IDE.

Any ideas what to do next?

####
#Date: Tue, 10 Oct 2017 14:42:22
#OSName: Windows 10 Pro 
#OSVers: 10.0
#OSBuild: 15063
#AppName: LabVIEW
#Version: 16.0f2 32-bit
#AppKind: FDS
#AppModDate: 2/13/2017 09:03 GMT
#LabVIEW Base Address: 0x00400000


InitExecSystem() call to GetCurrProcessNumProcessors() reports: 4 processors
InitExecSystem() call to GetNumProcessors()            reports: 4 processors
InitExecSystem()                                      will use: 4 processors
starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3590451742.90439940, (14:42:22.904399395 2017:10:10)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3590451742.90439940, (14:42:22.904399395 2017:10:10)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3590451742.90439940, (14:42:22.904399395 2017:10:10)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3590451742.90439940, (14:42:22.904399395 2017:10:10)]
starting LabVIEW Execution System 5 Thread 0 , capacity: 24 at [3590451744.55625770, (14:42:24.556257725 2017:10:10)]
starting LabVIEW Execution System 5 Thread 1 , capacity: 24 at [3590451744.55625770, (14:42:24.556257725 2017:10:10)]
starting LabVIEW Execution System 5 Thread 2 , capacity: 24 at [3590451744.55625770, (14:42:24.556257725 2017:10:10)]
starting LabVIEW Execution System 5 Thread 3 , capacity: 24 at [3590451744.55625770, (14:42:24.556257725 2017:10:10)]

<DEBUG_OUTPUT>
10/10/2017 14:43:21.731
DWarn 0x5C359BD0: no freeRange list or no elements
e:\builds\penguin\labview\branches\2016\dev\source\vi\cloneVI.cpp(412) : DWarn 0x5C359BD0: no freeRange list or no elements
minidump id: 5a131b3f-9e0e-4462-a33f-36b0f8b94d96
$Id: //labview/branches/2016/dev/source/vi/cloneVI.cpp#6 $

</DEBUG_OUTPUT>
0x006997BC - LabVIEW <unknown> + 0
0x10014A44 - mgcore_SH_16_0 <unknown> + 0
0x018B1176 - LabVIEW <unknown> + 0
0x018B18E5 - LabVIEW <unknown> + 0
0x01884365 - LabVIEW <unknown> + 0
0x018846A5 - LabVIEW <unknown> + 0
0x018A5903 - LabVIEW <unknown> + 0
0x01836EAA - LabVIEW <unknown> + 0
0x018AF415 - LabVIEW <unknown> + 0
0x009A1299 - LabVIEW <unknown> + 0
0x009B0166 - LabVIEW <unknown> + 0
0x00FE0918 - LabVIEW <unknown> + 0
0x01101929 - LabVIEW <unknown> + 0
0x00FDE022 - LabVIEW <unknown> + 0
0x013D2047 - LabVIEW <unknown> + 0
0x013D2ADB - LabVIEW <unknown> + 0
0x00BA92D1 - LabVIEW <unknown> + 0
0x01EB4817 - LabVIEW <unknown> + 0
0x01F661E5 - LabVIEW <unknown> + 0
0x01EB492C - LabVIEW <unknown> + 0
0x01EE0978 - LabVIEW <unknown> + 0
0x01F657A4 - LabVIEW <unknown> + 0
0x01F4CECB - LabVIEW <unknown> + 0
0x00AE5A05 - LabVIEW <unknown> + 0
0x0145A8F8 - LabVIEW <unknown> + 0
0x0145A91B - LabVIEW <unknown> + 0
0x00BA7981 - LabVIEW <unknown> + 0
0x01600F1B - LabVIEW <unknown> + 0
0x01605C71 - LabVIEW <unknown> + 0
0x01607D18 - LabVIEW <unknown> + 0
0x01EB4817 - LabVIEW <unknown> + 0
0x00CAF9BF - LabVIEW <unknown> + 0
0x00CB2189 - LabVIEW <unknown> + 0
0x00CB254E - LabVIEW <unknown> + 0
0x01EC0329 - LabVIEW <unknown> + 0
0x01F661E5 - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x00400000 ***
#** prop types: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\1abvi3w\user.lib\_LVCommon\LcProcessSpecs_class\utils\LcProcessSpecs_New.vi"
#** Loading: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\1abvi3w\user.lib\_LVCommon\LcProcessSpecs_class\utils\LcProcessSpecs_New.vi"
*** End Dump ***

<DEBUG_OUTPUT>
10/10/2017 14:43:26.805
DWarn 0x5C359BD0: no freeRange list or no elements
e:\builds\penguin\labview\branches\2016\dev\source\vi\cloneVI.cpp(412) : DWarn 0x5C359BD0: no freeRange list or no elements
minidump id: 9e03b61f-a952-492f-84a7-1c132e2646f1
$Id: //labview/branches/2016/dev/source/vi/cloneVI.cpp#6 $

</DEBUG_OUTPUT>
0x006997BC - LabVIEW <unknown> + 0
0x10014A44 - mgcore_SH_16_0 <unknown> + 0
0x018B1176 - LabVIEW <unknown> + 0
0x018B18E5 - LabVIEW <unknown> + 0
0x01839216 - LabVIEW <unknown> + 0
0x0183473D - LabVIEW <unknown> + 0
0x0183A560 - LabVIEW <unknown> + 0
0x01823ED2 - LabVIEW <unknown> + 0
0x018241BD - LabVIEW <unknown> + 0
0x01822664 - LabVIEW <unknown> + 0
0x01821D18 - LabVIEW <unknown> + 0
0x0183A3EB - LabVIEW <unknown> + 0
0x0181AE5D - LabVIEW <unknown> + 0
0x0181EECD - LabVIEW <unknown> + 0
0x0181F8BA - LabVIEW <unknown> + 0
0x010F4FED - LabVIEW <unknown> + 0
0x01100B34 - LabVIEW <unknown> + 0
0x0046C5D2 - LabVIEW <unknown> + 0
0x0046C7EA - LabVIEW <unknown> + 0
0x0046C8F5 - LabVIEW <unknown> + 0
0x00FDF8AD - LabVIEW <unknown> + 0
0x018298E4 - LabVIEW <unknown> + 0
0x018290BC - LabVIEW <unknown> + 0
0x018224B2 - LabVIEW <unknown> + 0
0x00FB1224 - LabVIEW <unknown> + 0
0x00FB1371 - LabVIEW <unknown> + 0
0x01822FFA - LabVIEW <unknown> + 0
0x018216C1 - LabVIEW <unknown> + 0
0x010F3551 - LabVIEW <unknown> + 0
0x01101117 - LabVIEW <unknown> + 0
0x00FDE022 - LabVIEW <unknown> + 0
0x013D2047 - LabVIEW <unknown> + 0
0x013D2ADB - LabVIEW <unknown> + 0
0x00BA92D1 - LabVIEW <unknown> + 0
0x01EB4817 - LabVIEW <unknown> + 0
0x01F661E5 - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x00400000 ***
#** Loading: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\1abvi3w\instr.lib\_BarajaDrivers\Tunable Lasers\VdYenistaT100S_class\Example\Example1.vi\2"
#** Loading: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\1abvi3w\instr.lib\_BarajaDrivers\Tunable Lasers\VdYenistaT100S_class\Example\Example1.vi"
*** End Dump ***

<DEBUG_OUTPUT>
10/10/2017 14:43:29.020
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 6b19dd9c-e4a7-433e-b736-08a8fdd75b3e
ExceptionCode: 0xC0000005

</DEBUG_OUTPUT>
0x7217146F - nierInterface <unknown> + 0
0x72175D75 - nierInterface <unknown> + 0
0x7217517A - nierInterface <unknown> + 0
0x762FA30D - KERNELBASE <unknown> + 0
0x77CC4AF1 - ntdll <unknown> + 0
0x77C857FD - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x00400000 ***
#** prop types: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\01_Application\MAIN_LaserCalV2.vi"
#** Loading: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\01_Application\MAIN_LaserCalV2.vi"
*** End Dump ***

 

Share this post


Link to post
Share on other sites

Hi,

I'm getting the same thing on three different LV 2015 built executables (but they have common code across the three), it's not a firewall issue as far as I can tell as the executable is running on the same PC that I'm trying to debug from, so it also shouldn't be a timeout or 'bandwidth' related issue.

Think I'm going to try use the simplest as the 'subject' of some experiments - removing all complex code and re-write it from the bottom up..

I suspect it has something to do with the LVOOP classes used to represent some of the test hardware. Or a missing external LVLIB

 

Kev

crash log report.txt

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.