debugging tools

debugging tools

[Conan Callen]

I want to start stepping through the selinux / lsm code so I can see what
is happening. Does anyone have any recomendations on kernel debugging
tools for doing this? I've been using vstudio on windows for years and the
windows sdk debugger for working with kernel code. So far the only
tool used on linux are emacs and vi ;)

Conan


--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: debugging tools

[Stephen Smalley]

On Thu, 4 Oct 2001, Conan Callen wrote:

> I want to start stepping through the selinux / lsm code so I can see what
> is happening. Does anyone have any recomendations on kernel debugging
> tools for doing this? I've been using vstudio on windows for years and the
> windows sdk debugger for working with kernel code. So far the only
> tool used on linux are emacs and vi ;)

Is this just a learning exercise or have you encountered a bug that you
want to track down?  If you really want some kind of kernel debugger, you
might try the SGI kGDB (see http://kgdb.sourceforge.net).

--
Stephen D. Smalley, NAI Labs
ssmalley@nai.com




--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: debugging tools

[Jose Nazario]

On Thu, 4 Oct 2001, Conan Callen wrote:

> I want to start stepping through the selinux / lsm code so I can see
> what is happening. Does anyone have any recomendations on kernel
> debugging tools for doing this?


look for kprof and kdb, lkcd should also be helpful:

http://oss.sgi.com/projects/

that should be a good place to start. i think that kprof uses the same
output format as gprof so it can use the same analysis tools.

hope that helps

____________________________
jose nazario						     jose@cwru.edu
	      	     PGP: 89 B0 81 DA 5B FD 7E 00  99 C3 B2 CD 48 A0 07 80
				       PGP key ID 0xFD37F4E5 (pgp.mit.edu)


--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

RE: debugging tools

[Westerman, Mark]

If you are trying to debug the kernel. You might want to
try uml (user mode linux) run linux as a process. I have 
not tried selinux on that yet, from my understanding it
is great for debugging kernel problems.


Mark Westerman
mark.westerman@csoconline.com

-----Original Message-----
From: Conan Callen [mailto:ccallen@windowpane.com]
Sent: Thursday, October 04, 2001 12:05 PM
To: selinux@tycho.nsa.gov
Subject: debugging tools


I want to start stepping through the selinux / lsm code so I can see what
is happening. Does anyone have any recomendations on kernel debugging
tools for doing this? I've been using vstudio on windows for years and the
windows sdk debugger for working with kernel code. So far the only
tool used on linux are emacs and vi ;)

Conan


--
You have received this message because you are subscribed to the selinux
list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov
with
the words "unsubscribe selinux" without quotes as the message.

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

RE: debugging tools

[Conan Callen]

Thanks for all the great pointers, I have a bit of research to do now.
User mode linux looks interesting, maybe I can spend some time on it
this weekend. This reminds me of an article (specific to windows NT) from
www.sysinternals.com showing how to have a usermode app execute kernel
code in user mode. It would be interesting to be able to apply this
same technique to linux.

Conan


--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

memset hangs part way through; called from early_init

[Chris Dumoulin]

Hi All,
I'm running a V2Pro-based development board, and I'm working on a linux 2.6.15 port.
Currently, the board hangs in the early_init function. Specifically, at the following line:
memset_io(PTRRELOC(&__bss_start), 0, _end - __bss_start);

This memset_io() call eventually calls memset() (from arch/ppc/lib/string.S) to zero the
region of memory. Using a BDI2000, I'm able to step through the assembly and see that
within memset, it enters a two-instruction loop where it is writing zeros to consecutive
memory locations. Everything is going fine, but after 10 or 20 iterations of the loop
(it's not consistent), everything blows up.

GDB reports the following:
------------------------------
(gdb) stepi

Program received signal SIG110, Real-time event 110.
0xc000b3e8 in memset ()
(gdb)
------------------------------

The BDI2000 reports the following:
------------------------------
*** MMU: address translation for 0xC000B3E8 failed
*** MMU: address translation for 0xC000B3E4 failed
*** MMU: address translation for 0xC000B3E8 failed
*** MMU: address translation for 0xC000B3E4 failed
*** MMU: address translation for 0xC000B3B0 failed
*** MMU: address translation for 0xDEADBEEF failed
*** MMU: address translation for 0xDEADBEEB failed
*** MMU: address translation for 0xDEADBEEF failed
*** MMU: address translation for 0xDEADBEEB failed
*** MMU: address translation for 0x00000000 failed
*** MMU: address translation for 0xDEADBEEF failed
*** MMU: address translation for 0xDEADBEEB failed
*** MMU: address translation for 0xDEADBEEF failed
*** MMU: address translation for 0xDEADBEEB failed
*** MMU: address translation for 0x00000000 failed
------------------------------

Here is my BDI2000 configuration file:
------------------------------
[INIT]



[TARGET]

JTAGCLOCK   0                   ;use 16 MHz JTAG clock

CPUTYPE     405 		;the used target CPU type

BDIMODE     AGENT   	        ;the BDI working mode (LOADONLY | AGENT)


BREAKMODE   HARD      	        ;SOFT or HARD, HARD uses PPC hardware breakpoint

STEPMODE    HWBP                ;JTAG or HWBP, HWPB uses one or two hardware breakpoints


MMU         XLAT 0xC0000000     ;enable virtual address mode

PTBASE      0x000000f0          ;address where kernel/user stores pointer to page table

STARTUP     RESET




[HOST]

IP          192.9.200.213


FILE        ppcboot.bin

FORMAT      BIN 0xfff80000 ;0x200000

START       0xfff80000 ; 0x200000

LOAD        MANUAL              ;load code MANUAL or AUTO after reset

DEBUGPORT   2001

DUMP        dump.bin            ;Linux: dump.bin must already exist and public writable



[FLASH]

WORKSPACE   0xffffd000

CHIPTYPE    STRATAX16

BUSWIDTH    16

CHIPSIZE    0x400000


[REGS]

IDCR1	0x010	0x011	;MEMCFGADR and MEMCFGDATA

IDCR2	0x012	0x013	;EBCCFGADR and EBCCFGDATA

IDCR3	0x014	0x015	;KIAR and KIDR

FILE    reg405gp.def
------------------------------

Any ideas would be appreciated.

Regards,
Chris Dumoulin

Re: memset hangs part way through; called from early_init

[Wolfgang Denk]

In message <200606011700.k51H0WJw014425@www-webmail1.magma.ca> you wrote:
>
> Currently, the board hangs in the early_init function. Specifically, at the following line:
> memset_io(PTRRELOC(&__bss_start), 0, _end - __bss_start);
...
> Any ideas would be appreciated.

See http://www.denx.de/wiki/view/DULG/LinuxCrashesRandomly

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
A princess should not be afraid -- not with a brave knight to protect
her.
	-- McCoy, "Shore Leave", stardate 3025.3

Debugging tools

[David H. Lynch Jr.]

    I have encountered one of the rare instances where I need/want more
debugging resources than an LED on an IO port.

    I am looking for some recommendations as well as understanding of
the lighter weight debugging tools that are available.
    I am dealing with a Xilinx V4 PPC405  FPGA. It is hosted in a
computer running Windows XP. Aparently there is a JTAG port
    on the device that emulates a JTAG parallel port on LPT3 on the host
side.

    I was hoping to be able to bring up gdb, download an elf file to the
target and step through a program to see where it is going off the rails.

    A bit of research suggests that there are gdbservers that bridge
between gdb and JTAG. But all the links I have found to rproxy seem to
be broken, and those for gdbproxy seem to be
    for other processors.

  

RE: Debugging tools

[Martin, Tim]

>=20
>     I was hoping to be able to bring up gdb, download an elf file to
the
> target and step through a program to see where it is going off the
rails.
>=20

Assuming you have the Xilinx EDK tools installed, there is a program
called xmd that acts as a standalone debugger or can communicate with
gdb over a socket.

>     A bit of research suggests that there are gdbservers that bridge
> between gdb and JTAG. But all the links I have found to rproxy seem to
> be broken, and those for gdbproxy seem to be
>     for other processors.

EDK builds example programs when you use the BSB.  You can download and
debug these programs as a test.  From EDK 7.1, Tools->Software Debugger.

Tim