apology - Re: rtems_semaphore_obtain error

[Jerry Needell]

What a bad place to leave out the key word NOT! My apologies for the  
pompous way the last line read! I meant to say that I have had very  
little experience with the use of semaphores or mutexes. I've sent  
some embarrassing posts in the past, but I think this was the worst.
-Jerry
On Jan 25, 2008, at 3:15 PM, Jerry Needell wrote:

> Sorry for misinformation , but I now see that the  
> condition :CORE_MUTEX_STATUS_CEILING_VIOLATED will result in the  
> Internal error.  So my real question is, does anyone have any tips  
> for tracking this down? I have (obviously) had much experience with  
> the semaphore handler.
> thanks
> - Jerry
>
>
>
> Jerry Needell wrote:
>> My application is entering Internal_error_Occurred  from  
>> rtems_semaphore_obtain. The call to rtems_semaphore obtain is  
>> coming from  internally from rtems as I am not using semaphore in  
>> my application. I have not tracked it down yet. thin interesting  
>> point is that in the source for rtems_semaphore_obtain, the las  
>> line is:
>>
>> return RTEMS_INTERNAL_ERROR;   /* unreached - only to remove  
>> warnings */
>>
>> but it is being reached!!
>>
>> Does anyone have any suggestions for potential culprits.
>>
>> BTW: I am using the sparc leon3 bsp in rtems 4.8
>>
>> - Jerry

--
Jerry Needell -- jerry.needell at unh.edu   telephone 603 862 2732
University of New Hampshire
Space Science Center - Morse Hall
39 College Road
Durham NH 03824
USA