Original from  Paul Edwards  to Denis Tonn on 10-29-1996
Original Subject: core dump

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

 PE> How do I get a dump for just my one task, when that one 
 PE> task has a trap-d?  BFN.  Paul.
 
 DT> DUMPPROCESS=x in your config.sys. Creates files PDUMP.001, PDUMP.002,
 DT> etc. 
 
PE> Thanks.
 
 DT> Not nearly as useful as it is in MVS. It only dumps the regs and the 
 DT> stack. No code or data areas. 
 
PE> Hmmm.
 
 DT> It is a little more useful under Warp 4, but I have not yet decided 
 
PE> Specifically?

 Some OS related control blocks for the process so you can get a 
little better idea of the environment. 

 DT> on how useful it would be without complete source/compile/link reorts 
 DT> files. 
 
PE> What's the problem with having them available when doing support?

 Nothing - if you are supporting a single program. But many times a 
"failure" involves much more than one "module". I have had many 
"problems" reported to me that are in application code or 
addon libraries or additional "API extender" type DLL's as "OS/2 or 
PM problems". There is no way I have the "source" for these addtional 
libraries or even the application. 

 DT> I suspect this will continue to be a developer only (not 
 DT> support) oriented facility. 
 
PE> It's a pretty fundamental thing an OS should provide for 
PE> application support purposes!  I tried it out under Warp 3, 
PE> and confirmed that the program data was not being dumped.  
PE> BFN.  Paul.

 Agreed. I would hate to do support on any OS (or application) without
at least some capabilities like this. OS/2 is probably the best of the
"desktop" systems I have worked with for these features, but still is 
a long way from the types of tools we expect in the mainframe world. 



   Denis       

 Certified OS/2 Engineer, Certified OS/2 Instructor, Certifiable....
 All opinions are my very own, IBM has no claim upon them
 
.
--- Maximus/2 3.01