> 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
-----Original Message-----
From: URIOT Didier DAPNIA
[mailto:[email protected]]
Sent: Thursday, February 23, 2006
9:42 AM
To: [email protected]
Subject: EZCA win32
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.
I’m just used some ezcaGet(…) and
ezcaPut(…) functions in a very small code.
I linked with ca.dll.
Compilation and linking worked.
But, the ezcaGet(…) function make the
code very unstable and I don’t understand why.
In the following example, ezcaGat(..) works, but when
I leave the main() procedure, the code systematically crashes!!!
int main (int argc, char *argv[])
{
double d;
ezcaGet(“epic_data1
",ezcaDouble,1,&d);
return 0;
}
Someone already meet this problem?
Thanks in advance