Hi Parmenides.. On Fri, Mar 30, 2012 at 19:00, Parmenides <mobile.parmenides@xxxxxxxxx> wrote: > > In the guest, 'mymodule.ko' is inserted again > > insmod mymodule.ko > > I found that the breakpoint set at mymodule.c:37 is triggered this > time surprisingly, and the 'insmod' didn't return immediately until > the gdb is given with another 'continue' command. > > (gdb) continue > > Then, the breakpoint doesn't triggered anymore as usual, Reading your above explanation, assuming that you inserted the symbol file into the right offset, I think you might found a bug in Qemu's gdb stub itself. I highly suggest you report this problem directly to qemu-devel list to get quick fix. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
