Messages in this thread | | | Subject | Re: kdb source level debugging | From | K S Sreeram <> | Date | 07 Nov 2002 03:36:13 +0530 |
| |
On Thu, 2002-11-07 at 03:43, slurn@verisign.com wrote: > The major problem is where to keep the source. Since you're debugging > the kernel, you probably don't want to keep the source on one of > the disks, as you may be debugging the filesystem, file cache > or disk driver. You can't use the buffer cache/file cache as that > would perturb the behavior of the system under test in an undesirable > fashion.
Why not keep the source compressed in memory. Since the primary purpose of this feature, would be debugging/learning, the extra memory usage will not be a problem on a 128 or 256 megs ram system. We can also come up with schemes to store only part of the source to allow source debugging of some parts of the kernel only.. but I wonder how much space the extra debug info would take up?
Regards Sreeram Tachyon Technologies
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |