Error in creating timer

[manish jain]

Actually, I think the error in my case is somewhat different. I was using
"fiprintf" statement in the call back function and  as this "fiprintf
"statement executed, the application seems to stuck there. Is this because
the context of callback function is different from the context where the
timer was initiated from?

Manish

On Sun, Apr 7, 2013 at 9:36 PM, Chris Johns <chrisj at rtems.org> wrote:

> Joel Sherrill wrote:
>
>>
>> Hindsight is 20/20 and in retrospect, I wish we had named that class
>> something else.
>>
>
> Agreed.
>
>
>  But I still have no idea what would be a better name
>> for the SuperCore Watchdog Handler class. If anyone has a suggestion
>> on what to rename it to which would both be clearer and avoid
>> confusion with Hardware Watchdogs, it would be appreciated.
>>
>
> Some suggestions ...
>
>  Timer
>  Fast_Timer
>  ISR_Timer
>
> The first is simple but does not bring in the fact these timers are safe
> under interrupts. Fast_Timers implies there is no context switch and
> ISR_Timers states these are for use in ISR contexts. For me Timer or
> ISR_Timer would be preferred.
>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20130407/629d1c82/attachment.html>