Re: kdb source level debugging

Re: kdb source level debugging

[K S Sreeram]

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

kdb source level debugging

[K S Sreeram]

hi

I am interested in implementing source-level debugging features for kdb.
I know that kgdb already does that, but kgdb is very inconvenient to use
compared to kdb as it requires two systems. Adding source level
debugging to kdb would allow me to understand the kernel source code
much better, since i would be able to trace thru the code and see it in
action.

has any such work already been done before? any tips on how this can be
implemented??

Thanks in Advance

Regards
Sreeram
Tachyon Technologies