| To: | "Grover, Andrew" <andrew.grover@xxxxxxxxx> |
|---|---|
| Subject: | Re: Source level debugging with kdb |
| From: | Keith Owens <kaos@xxxxxxxxxxxxxxxxx> |
| Date: | Thu, 21 Sep 2000 17:07:19 +1100 |
| Cc: | kdb@xxxxxxxxxxx |
| In-reply-to: | Your message of "Wed, 20 Sep 2000 22:43:47 PDT." <4148FEAAD879D311AC5700A0C969E8905DE368@orsmsx35.jf.intel.com> |
| Sender: | owner-kdb@xxxxxxxxxxx |
On Wed, 20 Sep 2000 22:43:47 -0700, "Grover, Andrew" <andrew.grover@xxxxxxxxx> 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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: kdb_read not exported, Keith Owens |
|---|---|
| Next by Date: | Re: Source level debugging with kdb, Scott Lurndal |
| Previous by Thread: | RE: Source level debugging with kdb, Grover, Andrew |
| Next by Thread: | Re: Source level debugging with kdb, Scott Lurndal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |