Experimental Physics and
Industrial Control System

Thank, for you answer.

In fact, I’m using the Easy CA library (compiled with BuilderC++ 6.0)  linked with ca.dll, cas.dll, com.dll, msvcr71.dll, msvcp71, cygwin1.dll.

All these DLL have been made with the 3.14.8 epics base compiled with VisualC++ Net.

So, perhaps, something is not compatible. I don’t know. (But, compilation and linking look like good).

Or the DLL have some problems. At present, the person which made them, have a look to check it.

Didier URIOT

> In the following example, ezcaGat(..) works, but when I leave the main() procedure, the code systematically crashes!!!

With this info it’s not easy to isolate between CA (which I maintain) and EZCA (for which I am not responsible).

To speed up fault isolation you might consider sending either:

A)     A stack trace (or traces for multiple threads) obtained from the Borland debugger.

B)     The source code for a simple program based only on the underlying CA interface, and not EZCA, that reproduces the problem.

Was the EPICS distribution also compiled by the Borland compiler?

Jeff

I need to develop a little application making some epics channel access under WindowsNT. I’m using Borland C++ compilator.

So, I used easy ca library for win32.