IDLE Task name error

[Joel Sherrill]

Derick Hammond wrote:

> Hello all:
> 
> I am looking for confirmation of a bug that I have found.  I recently 
> added a User Extension to my application to Display the task's name, id, 
> priority, stack size, and stack start address for debugging purposes.
> 
> I discovered that the IDLE task came back with garbage characters, but 
> my initial task was reported fine.
> 
> On further investigation I discovered the following mismatch:
> 
> In file: ./rtems-4.6.0pre3/cpukit/score/src/threadcreateidle.c
> 
> The global variable char * _Thread_Idle_name = "IDLE" is passed into the 
> _Thread_Initialize procedure which is expecting a type of Object_Name, 
> which results in the type mismatch.
> 
> However, I believe the desired behavior can be found by defining 
> _Thread_Idle_name as follows:
> 
> const Object_Name _Thread_Idle_name = 0x49444C45    /* 'I', 'D', 'L', 
> 'E' */
> If this is incorrect, or there is a better way to fix this, please let 
> know, as I would like to submit this in a Bug report to RTEMS.  If I 
> haven't already done so by posting this message ;-)

Well email to the list doesn't consitute a bug report. :)  Try the GNATS
database.

I think this is a real problem and don't see why this isn't
generating a warning in pre4.  Go ahead and attach a patch to the PR
when you file it and it will get applied.


> Cheers,
> Derick
> 


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985