NON-FATAL RUN-TIME ERROR: Unknown source position, thread id 0x000027D0: Parameter type incompatible with format specifier.

[Wolfgang]

I am running CVI 2013 SP1 with debugging level set to extended.

I have changed a formatting parameter in a FmtFile function call and now receive this error. I am wondering why CVI cannot handle this error better, i.e., inform me about the line number... One may have more than just one Fmt function...

[NeluF]

Hello Wolfgang,

Are you running the code in the Interactive Execution or as part of a program?

Thanks!

= Nelu F. || National Instruments.

[Wolfgang]

Hello Nelu,

it's part of a larger program, no interactive execution, and the formatting involves "%s%d%s%d[b8]...."

The error occured after I replaced a 32 bit integer by a 64 bit value and misplaced the [b8] (i.e. after the first %d instead of the second...). So the error is o.k. but it would have been useful if CVI would have informed me about the relevant line...

[NeluF]

Hello Wolfgang,

I tried reproducing the issue you've described and I received the following message:

I too tested with LabWindows/CVI 2013 SP1 (build 201), and I received the location information. Are you receiving a different message?

Regards,

= Nelu F. || National Instruments.

[Wolfgang]

Hi Nelu,

Thanks a lot for assistance!

Yes... I received exactly the message posted as subject... so what might be the difference? I am attaching my line of code and the error message popup below - the difference between your case and my case might be the length of the format string or the fact that there are several numbers involved in my case...??

[Wolfgang]

I just realized that you have used long (32 bit) - whereas I have used long long int (64 bit)...

[NeluF · Accepted solution]

Hello Wolfgang, 

I reproduced the error as you described it in the Debug64 configuration only. In the Debug configuration, the source location was specificed, so I have opened bug 472987 to track it. The issue appears to originate in LabWindows/CVI 2013.

Are you also seeing this issue in the Debug configuration? If so, could you please provide a sample?

Thanking you for your input,

Nelu F. || National Instruments.

[Wolfgang]

Hello Nelu,

I am glad you could reproduce the issue, thanks a lot!

Indeed, I am using Debug64 configuration.