Hi All,

We are trying to run KDB (4.0) on an Xscale kernel 2.4.19.
the Kernel was cross compiled with MV-Pro3.0 (GCC 3.2.1)
KDB is mostly working, but we are not getting correct output
when we try to look at the stack,  ps, or, backtrace. 
See below for further details,  
Any tips on how to fix?
Thanks in advance,
Jan
 
----- Original Message ----- 
From: "marks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 11, 2004 9:40 PM
Subject: xscale arm kernel 2.4.19-rmk7-ds3 with kdb integrated - question/help


> Hi Jan,
> 
> Last we spoke I had gotten kdb integrated with the xscale arm kernel
> 2.4.19-rmk7-ds3.  However, when we invoke kdb (CTRL-A in the minicom
> session) and try to use the "ps" command (similar to the ps command we all
> know and love) we get the following output:
> 
> Entering kdb (current=0xceb7c000, pid 223) due to Keyboard Entry
> kdb>
> kdb> ps
> Task Addr       Pid   Parent [*] cpu State Thread     Command
> 0xc0218000        0        0  1    0   R  0xc0218270  swapper
>   Error: does not match running process table (0xceb7c000)
> 0xc0538000        1        0  1    0   S  0xc0538270  init
>   Error: does not match running process table (0xceb7c000)
> 0xc05ce000        2        1  1    0   S  0xc05ce270  keventd
>   Error: does not match running process table (0xceb7c000)
> 0xc05ca000        3        1  1    0   S  0xc05ca270  ksoftirqd_CPU0
>   Error: does not match running process table (0xceb7c000)
> 0xc05c8000        4        1  1    0   S  0xc05c8270  kswapd
>   Error: does not match running process table (0xceb7c000)
> 0xc05c6000        5        1  1    0   S  0xc05c6270  bdflush
>   Error: does not match running process table (0xceb7c000)
> 0xc05c4000        6        1  1    0   S  0xc05c4270  kupdated
>   Error: does not match running process table (0xceb7c000)
> 0xcffda000        7        1  1    0   S  0xcffda270  mtdblockd
>   Error: does not match running process table (0xceb7c000)
> 0xcff3e000        8        1  1    0   S  0xcff3e270  rpciod
>   Error: does not match running process table (0xceb7c000)
> 0xced18000       26        1  1    0   S  0xced18270  LiS-2.16.18-1m:0?.?@
>   Error: does not match running process table (0xceb7c000)
> 0xcf012000       31        1  1    0   S  0xcf012270  inetd
>   Error: does not match running process table (0xceb7c000)
> 0xcf288000       35        1  1    0   S  0xcf288270  sctpd
>   Error: does not match running process table (0xceb7c000)
> 0xcf4ba000       40        1  1    0   S  0xcf4ba270  sshd
>   Error: does not match running process table (0xceb7c000)
> 0xcf196000       56        1  1    0   S  0xcf196270  sh
>   Error: does not match running process table (0xceb7c000)
> 0xcf3b0000       57        1  1    0   S  0xcf3b0270  syslogd
>   Error: does not match running process table (0xceb7c000)
> 0xcf376000       60       31  1    0   S  0xcf376270  in.telnetd
>   Error: does not match running process table (0xceb7c000)
> 0xcf33a000       61       60  1    0   S  0xcf33a270  sh
>   Error: does not match running process table (0xceb7c000)
> 0xcf21e000      143       31  1    0   S  0xcf21e270  in.telnetd
>   Error: does not match running process table (0xceb7c000)
> 0xced5a000      144      143  1    0   S  0xced5a270  sh
>   Error: does not match running process table (0xceb7c000)
> 0xcec0e000      181       31  1    0   S  0xcec0e270  in.telnetd
>   Error: does not match running process table (0xceb7c000)
> 0xcebea000      182      181  1    0   S  0xcebea270  sh
>   Error: does not match running process table (0xceb7c000)
> 0xcec6e000      189      182  1    0   S  0xcec6e270  vmstat
>   Error: does not match running process table (0xceb7c000)
> 0xcec10000      220       61  1    0   S  0xcec10270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xced6a000      221      144  1    0   S  0xced6a270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xcec52000      222      221  1    0   S  0xcec52270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xceb7c000      223      222  1    0   S  0xceb7c270 *hdctest
> 0xcec50000      224      220  1    0   S  0xcec50270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xced7a000      225      224  1    0   S  0xced7a270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xcec14000      226      220  1    0   Z  0xcec14270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xceefc000      227      220  1    0   Z  0xceefc270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xceb6e000      228      221  1    0   Z  0xceb6e270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xcec82000      229      221  1    0   Z  0xcec82270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xceb5e000      230      220  1    0   Z  0xceb5e270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xcecbe000      231      221  1    0   S  0xcecbe270  hdctest
>   Error: does not match running process table (0xceb7c000)
> 0xceafc000      232      220  1    0   S  0xceafc270  hdctest
>   Error: does not match running process table (0xceb7c000)
> kdb>
> 
> 
> The above "Error:" messages are coming from kdbmain.c.  I'm unsure why
> this is happening.  Perhaps there is some sort of disconnect between what
> kdb thinks a task_struct data structure (see kdbmain.c) looks like versus
> the actual definition of the data structure.
> 
>  -- Thanks,
> 
> Mark Sincerbox
> Adax, Inc.
> 1-510-548-7047 x129
> 
---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.

Reply via email to