Hi:

Thanks! But my program is also a kernel device driver module and isn't a process!

What should I do to watch the running details of a kernel function called in my own driver? Especially the driver initalization codes such as "register_netdev()" function. My linux kernel is 3.0.4 and KGDB enabled. Two PC linked by serial cable on serial port are there for debugging.


li, kunlun

---------- Post updated at 10:36 PM ---------- Previous update was at 09:12 PM ----------

Following are my actual methord of debugging into my own driver module from kernel:

at development end for example:

(gdb) br do_one_initcall
/*it will reply information such as "fn=0xd0a5c020", for example*/

(gdb)add-symbol-file path/to/rtl8139_driver.ko 0xd0a5c000
/*the address is geted from above fn-0x20*/

(gdb)hb 0xd0a5c000

when continue to the hard break, debugger can step into my driver module from kernel.

My question is whether this methord is right or not? What is the best or right methord?


thanks!
li, kunlun

---------- Post updated at 11:05 PM ---------- Previous update was at 10:36 PM ----------

(gdb) info br
Num Type Disp Enb Address What
1 breakpoint keep y 0xc0101104 in do_one_initcall
at init/main.c:671
breakpoint already hit 1 time
(gdb) n
671 in init/main.c
(gdb) n
668 in init/main.c
(gdb) s
671 in init/main.c
(gdb) n
674 in init/main.c
(gdb) step

Program received signal SIGSEGV, Segmentation fault.
0xf3983128 in ?? ()
(gdb)



and the related source code is here:

666 int __init_or_module do_one_initcall(initcall_t fn)
667 {
668 int count = preempt_count();
669 int ret;
670
671 if (initcall_debug)
672 ret = do_one_initcall_debug(fn);
673 else
674 ret = fn();


my linux kernel is 3.0.4;

Is there anyone who have any idea?