debugging modules

debugging modules

[ibm405gp]

Hello,

I want to develop a driver for a graphic card on a Walnut board.
>From now on, I've linked my source with the Linux kernel and debugged it
using a BDI2000.

I saw in a previous message that I would be able to debug modules
instead of generating the kernel each time.
Can somebody give me the procedure to follow?

thanks,

Laurent Mohin, Acterna

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: debugging modules

[Scott Anderson]

on 9/27/01 12:05 AM, ibm405gp at ibm405.linux@laposte.net wrote:
> I saw in a previous message that I would be able to debug modules
> instead of generating the kernel each time.
> Can somebody give me the procedure to follow?

I'll give you a quick pointer, but maybe someone else will give you
a better more detailed procedure.  The key is the add-symbol-file
command in gdb.  It takes an object file and an address.  Using
insmod -m (I believe - I'm aware from the office right now), you
can get the address of where a module gets loaded.  Then you use
add-symbol-file to teach gdb about this module and where it's at.

   Scott


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: debugging modules

[Peter Desnoyers]

Take a look in Documentation/i386/kgdb.  (a couple of the build options
may be different for PPC, but the gdb instructions are the same)

> on 9/27/01 12:05 AM, ibm405gp at ibm405.linux@laposte.net wrote:
> > I saw in a previous message that I would be able to debug modules
> > instead of generating the kernel each time.
> > Can somebody give me the procedure to follow?
>

--
.....................................................................
 Peter Desnoyers            (781) 457-1165   pdesnoyers@chinook.com
 Chinook Communications     (617) 661-1979   pjd@fred.cambridge.ma.us
 100 Hayden Ave, Lexington MA 02421

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/