Original from  Phil Crown  to All on 07-03-1996
Original Subject: sys3171

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

PC> I keep getting a SYS3171 error in a C++ program I am writing.
PC> 
PC> Is this in my program, or in TCP32DLL.DLL?
PC> 
PC> 07-03-1996  14:55:23  SYS3171  PID 0138
PC> E:\SO\OS2\C++\BNEWS\BNEWS.EXE
PC> 80000001
PC> 179633e4
PC> P1=00000002  P2=00716000  P3=XXXXXXXX  P4=XXXXXXXX  
PC> EAX=00716144  EBX=00710000  ECX=00717fb8  EDX=00717f74
PC> ESI=00000000  EDI=00717f88  
PC> DS=0053  DSACC=d0f3  DSLIM=1bffffff  
PC> ES=0053  ESACC=d0f3  ESLIM=1bffffff  
PC> FS=150b  FSACC=00f3  FSLIM=00000030
PC> GS=0000  GSACC=****  GSLIM=********
PC> CS:EIP=005b:1bf989da  CSACC=d0df  CSLIM=1bffffff
PC> SS:ESP=0053:00715fd4  SSACC=d0f3  SSLIM=1bffffff
PC> EBP=00716014  FLG=00012206
PC> 
PC> TCP32DLL.DLL 0001:000033e4

 The actual trap is in the DLL, but the "cause" could very easily be 
because of some parameters that you have passed on an API call. You
will need to walk the stack back to see. Either you can add an 
exception handler to capture the data at the trap, or you can generate
a system dump or even a process dump may have enough information if 
you have good application documentation. The dump formater will be on 
the CDROM of the GA version, or you can get the update for PF17 from 
the IBM Software FTP site. 



   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