I'm trying to debug a memory access error in a loadable device driver
that I wrote. When I use "kdbx -k vmunix.1 vmcore.1" on the crash dump
it shows me where the memory access occurs, but it will not allow me to
go to that point with the debugger and examine data, etc. Is there
anything I can do to enable these type of useful debug capabilities?
Or is the nature of kernel debugging such that you only get very limited
information. BTW, I'm using DU 4.0 on an Alphastation 255. My driver
is built with the -g1 flag so debug information should be present. Also,
I'm only set up to do a partial crash dump. Could that be my problem?
Any help is greatly appreciated. I will summarize.
Thanks,
Mike
----------------------------------------------------------------------
Michael Galuza
DeJarnette Research Systems mgaluza_at_dejarnette.com
401 Washington Ave Suite 700 Voice: +1(410)583-0680 x691
Towson, MD 21204 Fax: +1(410)583-0696
----------------------------------------------------------------------
Received on Wed Sep 24 1997 - 19:45:22 NZST