osdSufficentSpaceInPoolQuery fails on vxWorks 2 GB system

Bug #1090009 reported by Jeff Hill on 2012-12-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Jeff Hill

Bug Description

It appears that osdSufficentSpaceInPoolQuery isn't working correctly on vxWorks 2 GB systems. The WRS
memFindMax function should return an unsigned result. The osdSufficentSpaceInPoolQuery function
will work better if we cast the result from memFindMax to an unsigned number.

Jeff Hill (johill-lanl) on 2012-12-13
Changed in epics-base:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Jeff Hill (johill-lanl)
Jeff Hill (johill-lanl) on 2012-12-13
Changed in epics-base:
status: Confirmed → Fix Committed
Andrew Johnson (anj) wrote :

Fix committed in release.

Changed in epics-base:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers