Hi Mark, I agree that this should be fixed, it's just a matter of who can do it and when. That's why I marked this as a High priority bug.
Do you have the ability to run code on VxWorks at the moment? I don't since my office VME crate is turned off. The VxWorks targets use a completely different implementation based on the VxWorks API that I believe Marty used as the basis for the API for epicsMessageQueue, and RTEMS has a different one again, so I suspect your test might succeed on VxWorks. If you wanted to add your tests to epicsMessageQueueTest.c we'd certainly appreciate the help, and that might speed up someone fixing this.
Hi Mark, I agree that this should be fixed, it's just a matter of who can do it and when. That's why I marked this as a High priority bug.
Do you have the ability to run code on VxWorks at the moment? I don't since my office VME crate is turned off. The VxWorks targets use a completely different implementation based on the VxWorks API that I believe Marty used as the basis for the API for epicsMessageQueue, and RTEMS has a different one again, so I suspect your test might succeed on VxWorks. If you wanted to add your tests to epicsMessageQue ueTest. c we'd certainly appreciate the help, and that might speed up someone fixing this.