Source level debugging with kdb
Scott Lurndal
slurn at nanobiz.com
Thu Sep 21 01:04:02 PDT 2000
>
> On Wed, 20 Sep 2000 22:43:47 -0700,
> "Grover, Andrew" <andrew.grover at intel.com> wrote:
> >Source-level debugging would be very cool.
> >
> >BTW, can you describe more as to why there would be the
> >only-over-serial-port limitation? If it were possible to have source debug
> >for only a few modules (and the rest only symbols), that would fit in the
> >kernel image, but still not be too big...
>
> Source debug information is not stored in the running kernel, it is
> stored in vmlinux. The size of the running kernel is not the
> constraint, it is gdb's need to do I/O to access vmlinux. kdb does not
> allow I/O so gdb/vmlinux must be on a second machine.
>
You could preload the information from vmlinux
either at run-time prior to the first entry
of kdb (via insmod, for example) or at boot time
by reading the appropriate parts of vmlinux into
allocated memory. If you have the memory to spare...
scott
More information about the kdb
mailing list