what is An exception occured with in the external code called by a Call Library Node

[Student1]

An exception occured with in the external code called by a Call Library Node. This might have corrupted Labview's Memory. what is this error and how to get rid of it?

[rolfk]

Student1 wrote:

> An exception occured with in the external code called by a Call
> Library Node. This might have corrupted Labview's Memory. what is this
> error and how to get rid of it?

The dll called in that VI through a Call Library Node has done an
invalid operation which got captured by Windows and passed to the
LabVIEW exception handler. This exception handler is active since
LabVIEW 6.1. It basically means the DLL has tried to do some invalid
thing like a division by 0, bad pointer referencing or there might be a
debug breakpoint in the DLL, which would make little sense unless you
wrote the DLL and want to debug it. But the exception handler since
LabVIEW 6.1 will not pass this on to the registered system debugger, so
you need to debug it in anot
her application.

Rolf Kalbermatter

[Greg_McKaskle2]

> The dll called in that VI through a Call Library Node has done an
> invalid operation which got captured by Windows and passed to the
> LabVIEW exception handler. This exception handler is active since
> LabVIEW 6.1. It basically means the DLL has tried to do some invalid
> thing like a division by 0, bad pointer referencing or there might be a
> debug breakpoint in the DLL, which would make little sense unless you
> wrote the DLL and want to debug it. But the exception handler since
> LabVIEW 6.1 will not pass this on to the registered system debugger, so
> you need to debug it in another application.
>

If you want to avoid the exception being caught by LV, you can put a line

extFuncCatching= 0

into your .ini file and this should go
ahead and crash the LV process,
or it will crash into a debugger if you have one attached to the process
or DLL.

Greg McKaskle

[rolfk]

Greg McKaskle wrote:

> If you want to avoid the exception being caught by LV, you can put a line
>
> extFuncCatching= 0

Thanks Greg,

That is the thing I was looking for. It was a little annoying to go back
to LabVIEW 6.0 or write a separate test app every time I wanted to debug
a DLL I planned to use in LabVIEW. Or could you guys implement partial
exception handling such as catching everything except the int 3
breakpoint exception? It's unlikely that the breakpoint exception is an
unintended effect in a DLL.

Another thing I thought might help but turned out useless was to disable
debugging in the VI. But in hindsight I think it should be probably vice
versa. Catch exception in non-debugging mode and let it go in debugging
mode at least
if you have a system debugger installed. Never mind I can
now debug my DLLs with LabVIEW 7 as well.

Rolf Kalbermatter