In message <[EMAIL PROTECTED]>, Andrew Gallatin
writes:
>gdbmods does an ugly thing which is incredibly useful. It assumes
>that the modules you want to debug are sitting in your kernel build
>pool. So what it does is extract the build directory from the kernel
>(using strings), and runs a find
Giorgos Keramidas writes:
> On 2002-10-07 17:09, Ian Dowse <[EMAIL PROTECTED]> wrote:
> >
> > This is something I have been meaning to investigate for a while: [...]
> > Anyway, below is a proof-of-concept patch that does the basics, but
> > among other things, its logic for locating the ke
On 2002-10-07 17:09, Ian Dowse <[EMAIL PROTECTED]> wrote:
>
> This is something I have been meaning to investigate for a while: [...]
> Anyway, below is a proof-of-concept patch that does the basics, but
> among other things, its logic for locating the kernel module files
> needs a lot of work -
This is something I have been meaning to investigate for a while:
when gdb encounters a userland executable that uses shared libraries
it automatically adds the symbols from each library, so it seemed
likely that gdb could be made do the same thing with kernel modules.
I am aware of the existence
4 matches
Mail list logo
