Interactive Execution fails (miserably)

[Wolfgang]

Hello NI,

as reported yesterday here, legal C code (which is executed correctly when run in a program) causes serious errors in IW (this happens in CVI2013f1)

Since I don't want to hijack the other thread, I'll elaborate here.

Consider the following code:

enum months { Jan=1, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec };

enum months month;      

printf ( "%d\n", month=Sep );

This causes the following Debug Output:

HEAP[iw.exe]: Invalid allocation size - FFFFFF60 (exceeded fffdefff)
HEAP[iw.exe]: Invalid allocation size - FFFFFF52 (exceeded fffdefff)

The print statement isn't reached, so there is no interactive execution...

When compiled and linked as .c program I do get the printf output

[RobertoBozzolo]

This is just to point out that up to CVI2012SP1 this code is handled correctly in the IW.

[Wolfgang]

OK, I can add a few more details.

The result reported above is valid for Windows XP. Running the same at Win 7 64 bit Ultimate I do get different results:

Pushing the green RUN button in the IW the button is dimmed - but nothing happens. No printf output, no build error.

The button remains dimmed until I do a mouse click or an ALT+TAB 

[NeluF · Accepted solution]

Hello Wolfgang,

Thank you for bringing this issue to our attention. I opened bug report #435108. It will be fixed in a future version of LabWindows/CVI.

Best regards,

=Nelu F. || National Instruments.

[Wolfgang]

---

@NeluF wrote:

It will be fixed in a future version of LabWindows/CVI.

---

No false promises... there are so many open issues...

But thanks for adding it to The List.

[D-Cubed]

Hi Wolfgang,

I just wanted to follow up on this post to say this Bug fix will more than likely be included in the next release. 

Thanks,

Daniel

[Wolfgang]

indeed true, it has been fixed in CVI 2013 SP1