epicsTimerTest failure, windows vista 64, dual core SMP system

Bug #541360 reported by Jeff Hill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Fix Released
High
Jeff Hill

Bug Description

I just noticed that epicsTimerTest fails
o windows vista
o dual core SMP system

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

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

Here are the traces for all of the threads that were running
> Com.dll!tsDLList<epicsTimerQueueActiveForC>::remove(epicsTimerQueueActiveForC & item={...}) Line 230 + 0x9 bytes C++
  Com.dll!timerQueueActiveMgr::release(epicsTimerQueueActiveForC & queue={...}) Line 67 C++
  Com.dll!epicsTimerQueueActiveForC::release() Line 81 C++
  epicsTimerTest.exe!testAccuracy() Line 138 + 0x15 bytes C++
  epicsTimerTest.exe!main(int __formal=1, int __formal=1) Line 419 C++
  epicsTimerTest.exe!__tmainCRTStartup() Line 597 + 0x19 bytes C
  epicsTimerTest.exe!mainCRTStartup() Line 414 C
  kernel32.dll!7651e3f3()
  [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]
  ntdll.dll!76f8cfed()
  ntdll.dll!76f8d1ff()

  ntdll.dll!76f3039d()
  [Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
  kernel32.dll!764a1270()
  kernel32.dll!764a11d8()
> Com.dll!epicsEventWaitWithTimeout(epicsEventOSD * pSem=0x002e8380, double timeOut=0.99217767300000004) Line 123 + 0x12 bytes C
  Com.dll!epicsEvent::wait(double timeOut=0.99217767300000004) Line 72 + 0x14 bytes C++
  Com.dll!timerQueueActive::run() Line 71 C++
  Com.dll!epicsThreadCallEntryPoint(void * pPvt=0x001f234c) Line 42 + 0x13 bytes C++
  Com.dll!epicsWin32ThreadEntry(void * lpParameter=0x001f23b0) Line 498 + 0x11 bytes C
  msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes C
  msvcr80d.dll!_threadstartex(void * ptd=0x001f2ba0) Line 331 C
  kernel32.dll!7651e3f3()
  ntdll.dll!76f8cfed()
  ntdll.dll!76f8d1ff()

  ntdll.dll!76f3039d()
  [Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
  kernel32.dll!764a1270()
  kernel32.dll!764a11d8()
> Com.dll!epicsEventWaitWithTimeout(epicsEventOSD * pSem=0x002e84a0, double timeOut=1.7976931348623157e+308) Line 123 + 0x12 bytes C
  Com.dll!epicsEvent::wait(double timeOut=1.7976931348623157e+308) Line 72 + 0x14 bytes C++
  Com.dll!timerQueueActive::run() Line 71 C++
  Com.dll!epicsThreadCallEntryPoint(void * pPvt=0x001f2adc) Line 42 + 0x13 bytes C++
  Com.dll!epicsWin32ThreadEntry(void * lpParameter=0x001f2b40) Line 498 + 0x11 bytes C
  msvcr80d.dll!_callthreadstartex() Line 348 + 0xf bytes C
  msvcr80d.dll!_threadstartex(void * ptd=0x002ecfc8) Line 331 C
  kernel32.dll!7651e3f3()
  ntdll.dll!76f8cfed()
  ntdll.dll!76f8d1ff()

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

And the test output

1..40
# Testing timer accuracy
ok 1 - timerCount == nTimers
ok 2 - percentError < messageThresh
ok 3 - percentError < messageThresh
ok 4 - percentError < messageThresh
ok 5 - percentError < messageThresh
ok 6 - percentError < messageThresh
ok 7 - percentError < messageThresh
ok 8 - percentError < messageThresh
ok 9 - percentError < messageThresh
ok 10 - percentError < messageThresh
ok 11 - percentError < messageThresh
ok 12 - percentError < messageThresh
ok 13 - percentError < messageThresh
ok 14 - percentError < messageThresh
ok 15 - percentError < messageThresh
ok 16 - percentError < messageThresh
ok 17 - percentError < messageThresh
ok 18 - percentError < messageThresh
ok 19 - percentError < messageThresh
ok 20 - percentError < messageThresh
ok 21 - percentError < messageThresh
ok 22 - percentError < messageThresh
ok 23 - percentError < messageThresh
ok 24 - percentError < messageThresh
ok 25 - percentError < messageThresh
ok 26 - percentError < messageThresh
# average timer delay error -7.532058 ms

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

fixed in R3.14.11

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

R3.14.11 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.