Hi,
I read in kgdb_full_2.2.pdf, page 34, Section Tips, second bullet
"Avoid using the "n" command and single stepping (maybe
fixable in future). Set breakpoints where necessary."
I'm curious because I was trying to use "n" to single-step through
the bootup code in a 2.4.32 kernel on my xscale target when it
hang on line 599, an innocent assignment statement. Below is the
sequence. Could anyone share some insight or some general
comments on the Tip itself?
Thank you very much.
Wei
initrd_load () at init/do_mounts.c:894
894 create_dev("/dev/ram", MKDEV(RAMDISK_MAJOR, 0), NULL);
(gdb) n
895 create_dev("/dev/initrd", MKDEV(RAMDISK_MAJOR,
INITRD_MINOR), NULL);
(gdb)
897 return rd_load_image("/dev/initrd");
(gdb) s
rd_load_image (from=0xc0192500 "/dev/initrd") at init/do_mounts.c:590
590 int res = 0;
(gdb) n
597 unsigned short rotate = 0;
(gdb)
599 char rotator[4] = { '|' , '/' , '-' , '\\' };
(gdb)
____________________________________________________________________________________
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Kgdb-bugreport mailing list
Kgdb-bugreport@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
