The only time it seems to panic on me is during boot
when it loads from the initrd. In fact, that is reliably
reproducible. If the system boots and then the user does
an insmod, it works fine. Well, at least the few hundred
times I tried it and that's good enough for me.
Perhaps if I modify the initrd and have the insmod in
there do what your doing below, I might be able to keep
it up long enough by stepping to set the text segment in
gdb.
-bmb-
Douglas Kilpatrick wrote:
>
> On Fri, 27 Oct 2000, Brian Boerner wrote:
>
> > I'm using kgdb and want to debug a module that's causing an oops.
>
> From system:
>
> # insmod -m foo.o 2>&1 | grep '\.text\>'
>
> From gdb:
>
> (gdb) add-symbol-file ../foo.o 0xc482b050
>
> where 0xc482b050 is the address given for the .text segment by the insmod
> command.
>
> You will want to use gdb version 5 if you want to be able to look at
> global variables, and of course, compile with -g.
>
> Doug
> --
> dougk@xxxxxxxxxxx
> dkilpatr@xxxxxxx
|