Access violation in epicsTime::epicsTime (segmentation fault)
Bug #1377113 reported by
Uros Mitrovic
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
EPICS Base |
Won't Fix
|
Medium
|
Jeff Hill |
Bug Description
When calling function epicsTime:
Changed in epics-base: | |
status: | Triaged → Incomplete |
Changed in epics-base: | |
status: | Incomplete → Won't Fix |
To post a comment you must log in.
The C++ API for the epicsTime class can and does throw C++ exceptions to report errors. Your code must not allow those exceptions to escape from your C++ code up to the aSub record's process routine as may be happening here or your IOC will crash. Code running within the IOC that uses epicsTime objects must catch and handle any exceptions itself. If you don't want to do that, use the C API for epicsTime instead which catches them for you (but don't forget to check the error status return values that it returns instead).
The class definition in epicsTime.h defines two private exception classes that it might throw which are not derived from std::exception, but it can also throw std::exception classes as well. Once you've discovered what kind of exception is being thrown we can look into what could be causing it.
HTH,
- Andrew