-=> Quoting Russell to Peter, about Harmonic Mathematics <=-



 PF> After your program has terminated,  you can use the 

 PF> profile analysis tools to see which (and when,  if you 

 PF> like) the calls were made.



 RC> That sounds good, it should solve half my problem (determining what

 RC> system calls my programs are making).  But it won't allow me to

 RC> determine what system calls other peoples programs are making.  In

 RC> UNIX I often use strace to determine what programs do so I can tell

 RC> what is going wrong when they just give strange error messages and

 RC> exit... 



I don't know if this helps, but a utility called "go" lists the modules

currently in use and their dependancies.  You could watch this while the

program is running to at least see if any unusual dlls are being called.



I find it an invaluable utility, and helps ease the pain of coming from Linux

to OS/2.  Here's the program help output.



[c:\usr\sem]go -h

GO! v1.5 - (c) 1993-95 by Carsten Wimmer 



Usage: go  [argument]



Available commands:



   -pl   Process List        -k    Kill a Process

   -lpl  Process List with Paths      -ka   Kill all Instances

   -tl   Thread List                  -cp   Check for a Process

   -sl   Semaphore List               -j    Jump to a Process

   -sm   Shared Memory                -at   Application Type

   -ml   Module List                  -ut   Machine Uptime

   -mt   Module Dependency Tree       -df   Free Space on Drives

                     

   -lh   Long, detailed Help

   -la   GO! License Agreement

   

Gary   

... Since we all move so slow, why is it called rush hour?

--- Blue Wave/OS2 v2.30 [NR]