[RTEMS Project] #1785: Task name not correctly displayed by Capture Engine CLI

[RTEMS trac]

#1785: Task name not correctly displayed by Capture Engine CLI
--------------------+---------------------
 Reporter:  rsg     |       Owner:  chrisj
     Type:  defect  |      Status:  closed
 Priority:  normal  |   Milestone:  4.11
Component:  misc    |     Version:  4.10
 Severity:  normal  |  Resolution:  fixed
 Keywords:          |
--------------------+---------------------
Changes (by joel.sherrill):

 * status:  assigned => closed
 * resolution:   => fixed


Old description:

> The task name is not being reported correctly.  Using Virtex BSP, RTEMS
> 4.9 and the rtems_monitor, I get the following from ctlist:
>
> 1-rtems $ ctlist
> total 13
>  0a01000a   90  90  90 DELAY a---   0%   0% (15)
>  0a010007   30  30  30 Wevnt a---   0%   0% (5)
>  0a01000c   80  80  80 Wmsg a---   0%   0% (3)
>  0a010014   11  11  11 WRATE a---   0%   0% (9542)
>  0a010004  100 100 100 Wevnt a---   0%   0% (17)
>  0a010018   10  10  10 WRATE a---   0%   0% (1983)
>  0a010010   80  80  80 READY a---   0%   0% (2)
>  0a010002  100 100 100 Wevnt a---   0%   0% (64)
>  0a010019  100 100 100 DELAY a---   0%   0% (9809)
>  09010001  255 255 255 READY a---   0%   0% (172135)
>  0a010001  120 120 120 READY a---   0%   0% (5)
>  0a010011   80  80  80 READY a---   0%   0% (233)
>  0a01000b    1   1   1 READY a---   0%   0% (68596)
>
> Using Gaisler LEON3 BSP, RTEMS 4.10 and the shell, I get the following
> output (different sets of tasks, of course, and different BSPs, virtex
> and leon3, respectively):
>
> SHLL [/] # ctlist
> total 5
>  0a010003 @G?  10  10  10 Wmsg a--g   0%   0% (0)
>  0a010002 @G?  10  10  10 Wmsg a--g   0%   0% (0)
>  09010001 @G? 255 255 255 READY a--g   0%   0% (12332)
>  0a010005 @G?@
>                ?(@G?   1   1   1 Wmsg a--g   0%   0% (0)
>  0a010006 @G?@
>                ?(@G? 100 100 100 READY a--g %   `

>
> So, it isn't specific to BSP, nor is it real new...

New description:

 The task name is not being reported correctly.  Using Virtex BSP, RTEMS
 4.9 and the rtems_monitor, I get the following from ctlist:

 1-rtems $ ctlist
 total 13
  0a01000a   90  90  90 DELAY a---   0%   0% (15)
  0a010007   30  30  30 Wevnt a---   0%   0% (5)
  0a01000c   80  80  80 Wmsg a---   0%   0% (3)
  0a010014   11  11  11 WRATE a---   0%   0% (9542)
  0a010004  100 100 100 Wevnt a---   0%   0% (17)
  0a010018   10  10  10 WRATE a---   0%   0% (1983)
  0a010010   80  80  80 READY a---   0%   0% (2)
  0a010002  100 100 100 Wevnt a---   0%   0% (64)
  0a010019  100 100 100 DELAY a---   0%   0% (9809)
  09010001  255 255 255 READY a---   0%   0% (172135)
  0a010001  120 120 120 READY a---   0%   0% (5)
  0a010011   80  80  80 READY a---   0%   0% (233)
  0a01000b    1   1   1 READY a---   0%   0% (68596)

 Using Gaisler LEON3 BSP, RTEMS 4.10 and the shell, I get the following
 output (different sets of tasks, of course, and different BSPs, virtex and
 leon3, respectively):

 SHLL [/] # ctlist
 total 5
  0a010003 @G?  10  10  10 Wmsg a--g   0%   0% (0)
  0a010002 @G?  10  10  10 Wmsg a--g   0%   0% (0)
  09010001 @G? 255 255 255 READY a--g   0%   0% (12332)
  0a010005 @G?@
                ?(@G?   1   1   1 Wmsg a--g   0%   0% (0)
  0a010006 @G?@
                ?(@G? 100 100 100 READY a--g %   `

 So, it isn't specific to BSP, nor is it real new...

--

--
Ticket URL: <http://devel.rtems.org/ticket/1785#comment:4>
RTEMS Project <http://www.rtems.org/>
RTEMS Project