IDLE task has no name?

[Joel Sherrill]

Eric Norum wrote:

> I've adapted Chris Johns' capture package to provide a process  
> monitoring command for EPICS.  Here's a typical display:
>
>    PID   PRI STATE   %CPU %STK  NAME
> 09010001 255 READY   92.6    0
> 0a010022 100 READY    4.5   16  SPY
> 0a01001b 133 DELAY    1.6   24  scan0.1
> 0a01000d 109 DELAY    0.4   24  TSwdIncTimeSync
> 0a01001e 183 Wevnt    0.3   22  CAS-UDP
> 0a010004  10 Wevnt    0.1   22  ntwk
> 0a01001a 134 DELAY    0.0   24  scan0.2
> 0a010006  10 Wevnt    0.0   23  FECr
> 0a010018 136 DELAY    0.0   23  scan1
> 0a010019 135 DELAY    0.0   24  scan0.5
> 0a010017 137 DELAY    0.0   24  scan2
> 0a01001d 182 DELAY    0.0   16  CAS-beacon
> 0a010005  10 Wevnt    0.0   23  FECt
> 0a01000b 189 DELAY    0.0   24  taskwd
> 0a010016 138 DELAY    0.0   24  scan5
> 0a01001f 148 DELAY    0.0   23  seqAux
> 0a010021 148 Wmutex   0.0   19  CAC-event
> 0a010020 149 Wmutex   0.0   23  scanAcquisitionPll
> 0a01001c 181 Wevnt    0.0   22  CAS-TCP
> 0a010015 139 DELAY    0.0   24  scan10
> 0a010014 129 Wmutex   0.0   24  scanOnce
> 0a010013 139 Wmutex   0.0   24  EgRam
> 0a010012 149 Wmutex   0.0   24  dbCaLink
> 0a010011 128 Wmutex   0.0   24  cbHigh
> 0a010010 135 Wmutex   0.0   24  cbMedium
> 0a01000f 140 Wmutex   0.0   24  cbLow
> 0a01000e 129 Wmutex   0.0   23  timerQueue
> 0a01000c 109 DELAY    0.0   16  ts_syncC
> 0a01000a 149 Wmutex   0.0   20  L0
> 0a010009 149 Wmsg     0.0   24  singleTurn
> 0a010008 139 Wmutex   0.0   23  timerQueue
> 0a010007  50 Wevnt    0.0   23  RPCdrQueue
>
> There's one minor problem, though.  The 'idle' task has no RTEMS task  
> name -- or at least no printable characters in the name.   It would  
> be nice if it showed up as 'IDLE'.  Any suggestions on how to do this?
>

Are you on a little endian CPU?

See cpukit/score/src/threadcreateidle.c.  Idle has a name -- it is a string.
Looks like the printout is not honoring that some threads can have strings
for names based upon the API and type.

--joel