Keith Owens wrote: > > KDB (Linux Kernel Debugger) has been updated. > > ftp://oss.sgi.com/projects/kdb/download/v4.3/ > > Current versions are :- > kdb-v4.3-2.6.3-common-1.bz2 > kdb-v4.3-2.6.3-i386-1.bz2 > kdb-v4.3-2.6.3-ia64-1.bz2
How scriptable is kdb? Looking at the docs and google did not really help me find an answer, but feel free to point me to some docs I overlooked. What I want is the ability to log all accesses to a certain memory area from inside the kernel. AFAICS, breakpoints will not help me here because there are too few of them available (hardware limitation on i386). So I thought I could just unmap the page with the problematic memory area in it and catch all faults accessing this area with kdb, map the area again, execute the tripping instruction, unmap the area again and continue execution. I suspect a certain driver accessing the mmapped config space of a device it should leave alone. Unfortunately, reading from there can have side effects, otherwise I could have just made the covering page readonly. Is this possible with kdb or can I at least extend kdb in some way to achieve my goal? Thanks, Carl-Daniel --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
