Trap in GBM.dll when double clicking and exe or wpi file

[Gregg Young]

This trap only occurs on my SMP machine. It occurs in 3.16. It never occurred in the post 3.17 code until it was installed as my production version so it has something to do with the settings in my production version or a corrupted .dat or .ini file. The wpi was not associated so the internal viewer tried to open it (don't know if that was part of the issue). I have a trap dump but the ring 3 stack is gone.

[Gregg Young]

I can no longer reproduce this. I have made changes to DefaultView? which make this check the last check before opening a standard viewer (ie exe are now check before this)Also added a check and dialog for zero byte files. Somthing changed on my system and I don't know what that actually fixed this.

[rbri]

Have this trap here also (3.17).

From popuplog.os2

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

11-10-2009  21:15:27  SYS3170  PID 003d  TID 0001  Slot 0075
D:\PROGS\WEB\FIREFOX_3_5_4\FIREFOX.EXE
c0010001
1ffde3e1
EAX=00000004  EBX=5dc06f00  ECX=00000000  EDX=001e0122
ESI=5dc070a0  EDI=5dc06f00  
DS=0053  DSACC=f0f3  DSLIM=ffffffff  
ES=0053  ESACC=f0f3  ESLIM=ffffffff  
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1e933cd9  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:0011fef4  SSACC=f0f3  SSLIM=ffffffff
EBP=0011fef4  FLG=00210246

DOSCALL1.DLL 0003:0000e3e1

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

[rbri]

Upps wrong log entry

02-21-2010  13:45:08  SYS3171  PID 0046  TID 0001  Slot 007e
D:\PROGS\FM2\FM3.EXE
c0000005
1e3a1721
P1=00000002  P2=0001fe7c  P3=XXXXXXXX  P4=XXXXXXXX  
EAX=00000064  EBX=00000019  ECX=000003fc  EDX=0000006c
ESI=00000000  EDI=0000001a  
DS=0053  DSACC=f0f3  DSLIM=ffffffff  
ES=0053  ESACC=f0f3  ESLIM=ffffffff  
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1e3a1721  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:0001fe10  SSACC=f0f3  SSLIM=ffffffff
EBP=00000070  FLG=00010202

GBM.DLL 0002:00051721

[Gregg Young]

This occurs randomly when FM2 is attempting to view a binary file or a file it thinks is binary. It only happens when the internal viewer is used as the binary viewer. I contacted Heiko to get a gbm.map file. He indicated this was a known issue that should be fixed in GBM.dll version 1.73. I added a note about it in the troubleshooting section of the help file.

[Gregg Young]

CS 1636