Original from  Erwin Hogeweg  to Denis Tonn on 03-29-1997
Original Subject: Kernel debugger fails to

                         ---------------------------------------

  DT>  The debug kernel (and dump formatter and symbol files) for Warp 
  DT> Connect level are on the CDROM shipped with the product. 
 
EH> Aha, this I didn't know yet. Only, after reading the Debug Kernel Reference 
EH> manual, I am no longer sure that I really need/want this. 
EH> All I want to do is step through an suspicious API call ( 
EH> PrfWriteProfileData() ). I guess that all I have to do is 
EH> tell my debugger (IPMD) to include the *.SYM files. I just 
EH> haven't figured out yet how to do this so if you can give 
EH> me hint...

 I don't think IPMD uses the SYM files directly. It will generate them
for use by the debugger, but uses debug information in the executable 
directly. 

 The SYM files are just a binary representation of the data in the MAP
file. 

 I am not sure what you mean by "step through" an API call. I hope 
you don't mean single step through the kernel API. It is not something 
you would normally want to do. I would suspect that all you really
need to do is to use IPMD and your own source to stop just before the
call, look at all the variables involved, and then just after the API
returns and look at the RC and returned values. If it is good going
in, and bad coming out then report it as a bug in the API. You should
look at the data/code in hex/assembler rather than "source" to be sure
of what you are seeing though. 



   Denis       

 All opinions are my very own, IBM has no claim upon them
. 
. 
.
--- Maximus/2 3.01