General Time on Win32

Bug #541346 reported by Andrew Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Fix Released
Critical
Andrew Johnson

Bug Description

Not yet implemented.

OS: Win32

Version: R3.14.9

Original Mantis Bug: mantis-317
    http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=317

Revision history for this message
Andrew Johnson (anj) wrote :

It's not as bad as I originally thought, the code *is* implemented and it even compiles, but it fails at libCom initialization time — even Antelope won't run, so the build fails.

Revision history for this message
Andrew Johnson (anj) wrote :

The WIN32 clock has some kind of built-in PLL, which is updated periodically using an epicsTimer. Starting the PLL running initializes the timer which in turn causes epicsTime::getCurrent() to be called (so it can calculate the absolute time when the notification needs to be fired off). Now that generalTime is installed the code has to have registered itself as a time provider *before* starting the PLL.

I'm still getting a SEGFAULT when I run epicsTimerTest, but the exampleApp IOC does work so that probably isn't directly related to this bug.

Revision history for this message
Andrew Johnson (anj) wrote :

R3.14.10 released.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.