On Wed, Feb 18, 2009 at 1:36 AM, Lev Olshvang <levo@xxxxxxxxxxxx> wrote: > Hello List, > > I am trying to debug my module using kgdb > > After some retires I made a working host -target serial connection > > I use Ubuntu 7.10 as host, and Kernel 2.6.26 on target. > > The target indeed stops in boot waits for the gdb to set up breakpoints, > .... > > So I used set solib-path-search command in gdb to set up my driver > location and set a breakpoint within my driver. > Gdb warned me that currently this symbol is not visible and will become > visible on library load. > > Ok , I entered gdb> cont command, the target computer succesfully booted. > > Then I load my module on target hoping that gdb will hit a breakpoint > because the functions I asked to stop in are inside module initialization > code - but nothing happened. > > What do I miss here ? There's a chance that the breakpoint address you have set is no longer correct since symbol relocation happens during module insertion. For example: # cat /sys/module/ip_tables/sections/.init.text 0xe00fe000 # nm ip_tables.ko | grep init 0000000f T init_module What do you think? regards, Mulyadi. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
