Weird bug

[Galaxy_Stranger]

Howdy - aside from not getting GL mode to really work correctly on my machine, I've come across a very strange bug. I was testing how ZDoomGL would work with my vanilla ZDoom map. I went up to a door and opened it, and the game kicked me out with a big error message.

Says "ZDoom Very Fatal Error", here's part of the very long error:
Anybody have this problem before? Other than this, I don't think there are any other issues.


Code: ACCESS_VIOLATION
Tried to write address 00000039
Flags: 00000000
Address: 00428f97

Windows NT 5.0 Build 2195 Service Pack 4

GS=0000 FS=0038 ES=0023 DS=0023
EAX=02bd5bb8 EBX=05026da0 ECX=00000000 EDX=00000039
ESI=02bd5bb8 EDI=04fc3b88
EBP=05026da0 EIP=00428f97 ESP=0012f818 CS=001b SS=0023
EFlags=00210206
CF- PF+ AF- ZF- SF- TF- IF+ DF- OF- NT- RF+ VM- AC- VI- VP-

FPU State:
ControlWord=027f StatusWord=4020 TagWord=ffff
ErrorOffset=004879d1
ErrorSelector=009e001b
DataOffset=005c4cf8
DataSelector=ffff0023
Cr0NpxState=00000000

MM0=af2a38dc8ca40000
MM1=af2a5fe950e80000
MM2=8000000000000000
MM3=0000000000000000
MM4=0000000000000000
MM5=02bd5bb804fc3b88
MM6=05026da002bd5bb8
MM7=000000230012f818

Running threads:
00000120 at 00428f97*
000004dc
00000474
00000184
000004e4
00000434
000004f8
00000518
00000320
000004d8

Loaded modules:
00400000 - 00645fff *zdoomgl2.exe
77f80000 - 77ffafff ntdll.dll
7c4e0000 - 7c598fff KERNEL32.dll
77e10000 - 77e74fff USER32.dll
77f40000 - 77f7bfff GDI32.DLL
76b30000 - 76b6dfff comdlg32.dll
63180000 - 631e4fff SHLWAPI.DLL
78000000 - 78044fff msvcrt.dll
7c2d0000 - 7c331fff ADVAPI32.dll
77d30000 - 77d9dfff RPCRT4.DLL
71710000 - 71793fff COMCTL32.DLL
782f0000 - 78537fff SHELL32.DLL
77a50000 - 77b3bfff ole32.dll
75050000 - 75057fff WSOCK32.dll
75030000 - 75043fff WS2_32.DLL
75020000 - 75027fff WS2HELP.DLL
77570000 - 7759ffff WINMM.dll
10000000 - 10086fff fmod.dll
77410000 - 77422fff MSACM32.dll
69510000 - 695d6fff OPENGL32.dll
6fac0000 - 6fadefff GLU32.dll
51000000 - 51046fff DDRAW.dll
728a0000 - 728a5fff DCIMAN32.dll
00230000 - 003a2fff DevIL.dll
003b0000 - 003c2fff ILU.dll
51080000 - 510d5fff dsound.dll
77820000 - 77826fff VERSION.dll
759b0000 - 759b5fff LZ32.DLL
77560000 - 77567fff wdmaud.drv
77400000 - 77407fff msacm32.drv
5ef80000 - 5ef83fff KsUser.dll
775a0000 - 77625fff CLBCATQ.DLL
779b0000 - 77a4afff OLEAUT32.dll
03c80000 - 03cb3fff dinput8.dll
6f9a0000 - 6f9a7fff HID.DLL
77880000 - 7790dfff SETUPAPI.DLL
7c0f0000 - 7c151fff USERENV.DLL
04b90000 - 04ba0fff ctagent.dll
08550000 - 08573fff events.dll
6bfb0000 - 6bfb6fff midimap.dll

Bytes near EIP:
00428f87: 63 00 c1 fa 07 8b c2 5f c1 e8 1f 03 d0 8b c6 5e
00428f97: c6 04 0a 01 8b 4c 24 04 64 89 0d 00 00 00 00 83
00428fa7: c4 10 c2 04 00 90 90 90 90 8b 44 24 10 53 55 56

ZDoom version 2.0.47i

Command line:
zdoomgl2 robodoombeta2 +exec autoexec.cfg -skill1
IWAD: zdoomgl.wad

Current map: MAP01

viewx = -301226742
viewy = 139482499
viewz = 2359296
viewangle = 16056320

Possible call trace:
00428f97 BOOM
0045825b call 00428f20

[timmie]

Hmm, don't suppose you'd be able to upload the map somewhere? If not, email it to me: zdoomgl@zdoom.org... I'm going through a big bug-fixing phase right now to try and get things ironed out as much as possible for when I do the next full release :)

[Galaxy_Stranger]

It's about 2 and a half megs:

http://planetrobotech.no-ip.com

Let me know when you snag it, I'm juggling computers right now, and I don't know how long it'll be up.

[timmie]

Ok, got it. No problems so far, so whatever it was might have already been fixed. Also, love the music :)

[Galaxy_Stranger]

Ok - I was using ZDOOMGL2.exe

what's that in there for? heh, it looks better than zdoomgl.exe in software mode.

[Galaxy_Stranger]

btw - i'm trying to get the gl renderer to work on my machine. I've got a TNT2. Izzit a driver problem or does my card not like GL?

[timmie]

Ah, I just started calling it zdoomgl2.exe when I got the latest update from Randy because so much stuff had changed and I didn't want to overwrite the old zdoomgl.exe. I'm thinking the bug might have been fixed just recently, actually, so the fix won't be available quite yet...