instruction access exception

Joel Sherrill joel.sherrill at oarcorp.com
Fri Apr 13 17:06:56 UTC 2007


Till Straumann wrote:
> IIRC timers run at ISR context. You don't call printf
> from the timer routine itself, do you?
> That would definitely crash...
>
>   
It would also help to know the architecture along with what code
is at that address.  The trap means something is wrong.
> -- Till
>
> hwulf at et-inf.fho-emden.de wrote:
>   
>> Hi,
>>
>> I created a RTEMS program with some semaphores, tasks and message queues.
>>
>> For debugging reasons, I included many printf() statements like this:
>>
>> #ifdef DEBUG
>> printf("createTimer: line: %i: Obtaining Semaphore timer_sem_id\n", __LINE__);
>> #endif
>>
>>
>> Now, when I start the program with #define DEBUG, the program stops at  
>> an irregular instruction and the following lines are printed to the  
>> console:
>>
>> Unexpected trap <0x01> at address 0xd0142300c
>> instruction access exception
>>
>> Program exited normally.
>>
>>
>> When I compile the program without #define DEBUG instead, the program  
>> runs just as expected.
>>
>> Has anyone an idea what's wrong with the printf() statements?
>> Am I overflowing the stack or something like that?
>>
>> Thank you very much in advance.
>>
>> Kind regards,
>>   Hank
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at rtems.com
>> http://rtems.rtems.org/mailman/listinfo/rtems-users
>>   
>>     
>
>
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.com
> http://rtems.rtems.org/mailman/listinfo/rtems-users
>   




More information about the users mailing list