Hi Mark,
I am using the master branch of areaDetector with EPICS 7 with no problems. The modules I announced in this tech talk message
https://epics.anl.gov/tech-talk/2018/msg00156.php (areaDetector, ADCore, ADSupport) and this tech-talk message
https://epics.anl.gov/tech-talk/2018/msg00203.php (ADPilatus, ADAndor, ADPerkinElmer, ADLightField, ADPointGrey, ADSimDetector, ADProsilica) are all compatible with EPICS 7.
You said you are running pvaDriver R1-3. That is the problem, that is from July 5, 2017, well before EPICS 7 was released.
The master branch of pvaDriver has the fixes needed for EPICS 7. You should use that until pvaDriver R1-4 is released.
Mark
Mark,
At some point I thought that you had said that you had built epics 7 and a recent version of Area Detector and it all worked.
Can you correct me if this is an incorrect memory?
Asking since I had been trying to compile Epics base 7.0.1.1 and AD R3-1 and R3-2 and while everything compiles, all my AD softioc’s crash and burn if I build them against the pvadriver-1-3 with a null this-> pointer when the pvadriver
is instantiated attempting to create a mutex lock. Happen with MSVC 2017 and 2010. And happens if I used EPICS-CPP-4.7.0. and not the versions in epics 7.
Note sure if I should be looking in the epics base code for an issue of if this has to be in the pvadriver since everything else seems to work if I don’t build against it.