explain EPICS exit issues in CA ref manual

Bug #541192 reported by Jeff Hill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Fix Released
Wishlist
Andrew Johnson

Bug Description

A CA client application that calls epicsExit *must* install an EPICS exit handler that calls ca_context_destroy only *after* calling ca_create_context(). This will guarantee that the EPICS exit handlers get called in the correct order. Perhaps on vxWorks (and on RTEMS)the soft reboot issues may be compelling. A CA client application that runs on these OS may need to have an EPICS exit handler that call ca_context_destroy().

Additional information:
Somewhat related to #161

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

Tags: ca 3.14
Revision history for this message
Jeff Hill (johill-lanl) wrote :

A program running in an IOC context must delete all of its channels prior to calling ca_context_destroy. Otherwise, database scan tasks will continue to post monitors into a non-existent event queue. That will cause a crash.

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

Fixed for R3.14.10.

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.