| To: | Scott Lurndal <slurn@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Source level debugging with kdb |
| From: | Keith Owens <kaos@xxxxxxxxxxxxxxxxx> |
| Date: | Thu, 21 Sep 2000 19:45:25 +1100 |
| Cc: | andrew.grover@xxxxxxxxx (Grover Andrew), kdb@xxxxxxxxxxx |
| In-reply-to: | Your message of "Thu, 21 Sep 2000 01:04:02 PDT." <200009210804.BAA04505@pendragon.eng.nanobiz.com> |
| Sender: | owner-kdb@xxxxxxxxxxx |
On Thu, 21 Sep 2000 01:04:02 -0700 (PDT), Scott Lurndal <slurn@xxxxxxxxxxx> wrote: >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... But then you have to teach gdb to read from memory instead of from a file. The whole problem is the design of gdb, it runs as a normal application and issues system calls to do I/O and talk to the user. System calls require kernel support but kdb has stopped the kernel. Don't even think about embedding gdb into the kernel, shudder. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Source level debugging with kdb, Scott Lurndal |
|---|---|
| Next by Date: | Re: Source level debugging with kdb, Andi Kleen |
| Previous by Thread: | Re: Source level debugging with kdb, Scott Lurndal |
| Next by Thread: | Re: Source level debugging with kdb, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |