Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Csonicgo

Bug Report

Recommended Posts

I have nothing else to add to this report.

Eternity caused an Access Violation Exception (0xc0000005)
in module Eternity.exe at 001b:004b4ff7.

Error occurred at 6/5/2011 20:02:54.

Operating system: 5.1.2600
1 processor, type 586.
28% memory in use.
2040 MB physical memory.
1451 MB physical memory free.
3411 MB page file.
2869 MB paging file free.
2048 MB user address space.
1979 MB user address space free.
Access violation at 02075d74. The memory could not be read.

Context:
EDI:    0xa7ed0000  ESI: 0x000003ff  EAX:   0xfffff5e6
EBX:    0x004b4ca0  ECX: 0xffffa7ed  EDX:   0x00000000
EIP:    0x004b4ff7  EBP: 0x0208bdb8  SegCs: 0x0000001b
EFlags: 0x00010296  ESP: 0x0012fdf8  SegSs: 0x00000023

Bytes at CS:EIP:
8b 44 8d 08 8b d0 c1 fa 18 0f b6 ca 8b d0 c1 fa 

Stack:
0x0012fdf8: 000006ed 000006ed 01ea7028 0208bdb8 ........(p......
0x0012fe08: 01ea7028 01000001 00005001 004b4ca0 (p.......P...LK.
0x0012fe18: 004b553c 0012fe20 0208bdb8 00000000 <UK. ...........
0x0012fe28: 00000000 01e34500 00000001 0040b528 .....E......(.@.
0x0012fe38: 00000000 0052b3c0 0208bdb8 00000000 ......R.........
0x0012fe48: 78552253 00000004 0051ed80 00000000 S"Ux......Q.....
0x0012fe58: 01ffffff 0000000a 004ae3e7 003a8d68 ..........J.h.:.
0x0012fe68: 003a8d68 003a8d68 0012fe80 0040bb04 h.:.h.:.......@.
0x0012fe78: 78552253 785460ad 00000000 00000000 S"Ux.`Tx........
0x0012fe88: ffffffff 0012fee4 00000018 00000018 ................
0x0012fe98: 004b8677 0157e562 004e7b30 00000018 w.K.b.W.0{N.....
0x0012fea8: 0012ff20 0012ff00 0000000a 00000000  ...............
0x0012feb8: 004b7f3b 004e7b30 78552253 785460ad ;.K.0{N.S"Ux.`Tx
0x0012fec8: 00000000 00000000 00000000 00000000 ................
0x0012fed8: 00000000 00000000 00000000 0157e57a ............z.W.
0x0012fee8: 000003e2 004e6ea8 00000000 00000000 .....nN.........
0x0012fef8: ffffffff 00416d00 0051ed80 0041bea1 .....mA...Q...A.
0x0012ff08: 004ccf64 0041beb2 0041b52d 004e6ea0 d.L...A.-.A..nN.
0x0012ff18: 004e7b4c 004e7b30 0157ec4c 00000001 L{N.0{N.L.W.....
0x0012ff28: 0012ff7c 00000000 00e127d0 00000000 |........'......
0x0012ff38: 004c951d 004c9534 004e78f0 004e78fc ..L.4.L..xN..xN.
0x0012ff48: 00000000 0041bc05 004aa8c5 004af3e8 ......A...J...J.
0x0012ff58: 0157ec4c 00000001 00000000 0012ff58 L.W.........X...
0x0012ff68: 0012fa1c 0012ffb0 004ca030 004ff500 ........0.L...O.
0x0012ff78: 00000000 0012ffc0 004c97ca 00000002 ..........L.....
0x0012ff88: 00352b60 00353060 febc34a8 80000001 `+5.`05..4......
0x0012ff98: 00add9e4 7ffda000 00add9e4 00000000 ................
0x0012ffa8: 0012ff90 8b641628 0012ffe0 004c9989 ....(.d.......L.
0x0012ffb8: fee12650 00000000 0012fff0 7c817077 P&..........wp.|
0x0012ffc8: 80000001 00add9e4 7ffda000 80544cfd .............LT.
0x0012ffd8: 0012ffc8 89b7a020 ffffffff 7c839ad8 .... ..........|
0x0012ffe8: 7c817080 00000000 00000000 00000000 .p.|............
0x0012fff8: 015a6930 00000000                   0iZ.....


===== [end of CRASHLOG.TXT] =====

Share this post


Link to post
Csonicgo said:

I have nothing else to add to this report.

No dr.watson log? There is even no EE version in the report.

Share this post


Link to post
entryway said:

No dr.watson log? There is even no EE version in the report.


It's all that EE spit out at me when it crashed. I simply copy/pasted what it gave me. :(

Share this post


Link to post

A while ago I got one too, which I forgot to submit. This is with the latest release version (3.40.11). Happened during some random running around in a WIP, but could not reproduce it so chalked it up to a fluke.

Eternity caused an Access Violation Exception (0xc0000005)
in module Eternity.exe at 001b:004791ff.

Error occurred at 5/27/2011 23:21:42.
C:\games\Eternity\Eternity.exe, run by Gaston Lahaut.
Operating system: 5.1.2600
1 processor, type 586.
65% memory in use.
1023 MB physical memory.
357 MB physical memory free.
1697 MB page file.
1214 MB paging file free.
2048 MB user address space.
1927 MB user address space free.
Access violation at 00000000. The memory could not be read.

Context:
EDI:    0x00000000  ESI: 0x000000e0  EAX:   0x0012fbf0
EBX:    0x06e43440  ECX: 0x00000000  EDX:   0x00000000
EIP:    0x004791ff  EBP: 0x00000000  SegCs: 0x0000001b
EFlags: 0x00210246  ESP: 0x0012fbb8  SegSs: 0x00000023

Bytes at CS:EIP:
83 3a 05 7d 34 8b a8 50 01 00 00 85 ed 89 2d f0 

Stack:
0x0012fbb8: 9f97d69f 00000000 0709fdc8 00000000 ................
0x0012fbc8: 00000000 000000e0 00000000 00000000 ................
0x0012fbd8: 000000e0 00000007 04dbd098 c489dd53 ............S...
0x0012fbe8: c66b8aa4 c3a20000 fea00000 febbffff ..k.............
0x0012fbf8: 000004b0 00000496 000700e0 000000cf ................
0x0012fc08: ffffffff ffffffff 00000000 00000000 ................
0x0012fc18: 0000000d 0000000b 00000067 0000006a ........g...j...
0x0012fc28: 004ca8a8 00000000 00000000 00000000 ..L.............
0x0012fc38: 00000000 fc000000 00000000 00000000 ................
0x0012fc48: 00000000 00000000 00000000 00000000 ................
0x0012fc58: fc000000 c5560000 00000000 00000007 ......V.........
0x0012fc68: 004ca8a8 00000000 00000000 00000000 ..L.............
0x0012fc78: 00000000 01508f00 00000000 00000000 ......P.........
0x0012fc88: 00000000 00000000 00000000 00000000 ................
0x0012fc98: fc000000 c5560000 00000000 00000007 ......V.........
0x0012fca8: 0011caab 04c5d650 0000e800 00000800 ....P...........
0x0012fcb8: 00000000 00000000 00000000 00000000 ................
0x0012fcc8: ffffffff ffffffff 00000000 00000000 ................
0x0012fcd8: 00000000 00000000 000008d4 000008d4 ................
0x0012fce8: ffffffff 00000005 00000000 00000000 ................
0x0012fcf8: 00000000 05032d78 0000001a 04de3028 ....x-......(0..
0x0012fd08: 00000000 00000000 00000000 00000000 ................
0x0012fd18: 00000000 00000000 00000000 00000000 ................
0x0012fd28: 00000000 00000000 00000000 00000000 ................
0x0012fd38: 00000380 00000000 00000000 00000000 ................
0x0012fd48: 00000007 00000000 00000000 00000000 ................
0x0012fd58: ffffffff 00000000 00000000 00000000 ................
0x0012fd68: 00000000 00000000 c3a20000 c3b00000 ................
0x0012fd78: 00000000 00000000 00000005 00000020 ............ ...
0x0012fd88: 0000000c 00000000 00000000 00000000 ................
0x0012fd98: 05030000 00000000 00000000 0012ff6c ............l...
0x0012fda8: 004ae24b 00000000 004793bf 80004445 K.J.......G.ED..
0x0012fdb8: fbb11565 c51d56f2 0709fdc8 00000000 e....V..........
0x0012fdc8: 0709feb8 004793bf 0000443f fbb11565 ......G.?D..e...
0x0012fdd8: c51d56f2 0709feb8 00000000 070a0458 .V..........X...
0x0012fde8: 004793bf 00004441 fbb11565 c51d56f2 ..G.AD..e....V..
0x0012fdf8: 070a0458 00000001 070a04d0 004793bf X.............G.
0x0012fe08: 0000444d fbb11565 c51d56f2 070a04d0 MD..e....V......
0x0012fe18: 00000000 070a18f8 004793bf 0000444e ..........G.ND..
0x0012fe28: fbb11565 c51d56f2 070a18f8 00000001 e....V..........
0x0012fe38: 070a1970 004793bf 00004479 fbb11565 p.....G.yD..e...
0x0012fe48: c51d56f2 070a1970 00000000 070a77a8 .V..p........w..
0x0012fe58: 004793bf 0000447a fbb11565 c51d56f2 ..G.zD..e....V..
0x0012fe68: 070a77a8 00000000 070b1e10 004793bf .w............G.
0x0012fe78: 00004543 fbb11565 c51d56f2 070b1e10 CE..e....V......
0x0012fe88: 00000001 070b1e88 004793bf 000046a6 ..........G..F..
0x0012fe98: fbb11565 c51d56f2 070b1e88 00000001 e....V..........
0x0012fea8: 070b1f00 004793bf 000046a7 fbb11565 ......G..F..e...
0x0012feb8: c51d56f2 070b1f00 00000000 07102360 .V..........`#..
0x0012fec8: 004793bf 000046a8 fbb11565 c51d56f2 ..G..F..e....V..
0x0012fed8: 07102360 00000001 071023d8 004793bf `#.......#....G.
0x0012fee8: 0000515c fbb11565 c51d56f2 071023d8 \Q..e....V...#..
0x0012fef8: 00000001 07102450 004793bf 0000515d ....P$....G.]Q..
0x0012ff08: fbb11565 c51d56f2 07102450 0052ab00 e....V..P$....R.
0x0012ff18: 00000000 0047eb9d 0000515e 01562fd8 ......G.^Q.../V.
0x0012ff28: 00000001 0012ff7c 00000000 00416bb5 ....|........kA.
0x0012ff38: 0052ab00 00000000 00418db9 00490e13 ..R.......A...I.
0x0012ff48: 004955e7 00000008 003d3d78 9f97d25f .UI.....x==._...
0x0012ff58: 01562fd8 00000001 00000000 0012ff54 ./V.........T...
0x0012ff68: 0012f7c4 0012ffb0 004ac0fe 9fcb153b ..........J.;...
0x0012ff78: 00000000 0012ffc0 004ac2b0 00000008 ..........J.....
0x0012ff88: 003d3d78 003d2f40 9f97d2e3 00320038 x==.@/=.....8.2.
0x0012ff98: 00300036 7ffd7000 00300036 00000000 6.0..p..6.0.....
0x0012ffa8: 0012ff90 f881f8bc 0012ffe0 004ac0fe ..............J.
0x0012ffb8: 9fcb175b 00000000 0012fff0 7c7e7077 [...........wp~|
0x0012ffc8: 00320038 00300036 7ffd7000 8054b738 8.2.6.0..p..8.T.
0x0012ffd8: 0012ffc8 86071c60 ffffffff 7c809ad8 ....`..........|
0x0012ffe8: 7c7e7080 00000000 00000000 00000000 .p~|............
0x0012fff8: 004ac3f9 00000000                   ..J.....

Share this post


Link to post

Not to be too rude or anything, but guys, this shit is useless. Really the best thing is building a debug version, running it in a debugger, reproducing the issue and sending the resulting stack trace. It's practically impossible to figure anything out from these crash logs.

Share this post


Link to post
Ladna said:

Not to be too rude or anything, but guys, this shit is useless. Really the best thing is building a debug version, running it in a debugger, reproducing the issue and sending the resulting stack trace. It's practically impossible to figure anything out from these crash logs.



I very much doubt that many of the people experiencing such a crash would even be able to get a debugger running. But I agree that crash logs without a stack trace are useless (which is why ZDoom adds one...)

Share this post


Link to post
Ladna said:

It's practically impossible to figure anything out from these crash logs.

Oh really?

Graf Zahl said:

I very much doubt that many of the people experiencing such a crash would even be able to get a debugger running. But I agree that crash logs without a stack trace are useless (which is why ZDoom adds one...)

Without a stack trace? That's precisely what all that hex is. Well, it's a stack DUMP anyways. How do you get a "trace" out of a program compiled in release mode? It's not like there's debug information to use to get function names.

Anyway these are useful so long as they tell me what version of the EXE they're using and are accurate in giving me that information.

All I have to do is put the addresses you see at the crash location and in the stack dump into IDA Pro and it'll take me right to where Eternity crashed. I can then look up the name of the function I am inside in the .map file for that build. So, kindly don't tell my users that this isn't helpful when it actually is extremely useful.

Watch my system of reasoning as it played out in IRC:

<Quasar`> 8B  44 8D 08 <- look familiar?
<Quasar`> Bytes at CS:EIP:
<Quasar`> 8b 44 8d 08
...
<Quasar`> this-> ECX: 0xffffa7ed
<Quasar`> is the problem
<Quasar`> that's texturecol.
<Quasar`> and it's negative.
<Quasar`> that shouldn't ever happen.
<CSG> ECX STRIKES AGIN
<CSG> :(
<Quasar`>          column = (column_t *)((byte *)patch +
<Quasar`>             SwapLong(patch->columnofs[texturecolumn]));
<Quasar`> I believe this is the line of code it crashed on.
<Quasar`> the [ebp+ecx*4+8] is patch->columnofs[texturecolumn]
<Quasar`> columnofs == offset 8 into patch_t I believe.
<CSG> and how would that crash?
<CSG> :P
<Quasar`> because texturecolumn is negative.
<Quasar`> 0xffffa7ed
<Quasar`> that is -22547
All of this information derived from his post, in concert with the .idb and .map.

The problem is, people aren't recording enough info about what they were doing when they got the crash.

CSonicGo can't figure out whether or not he might have been running a particular infamously bad mod at the time (his crash is inside V_DrawPatchInt, which, if it had a bleeding obvious bug, Eternity would crash here all the time - I suspect garbage in, garbage out).

Mordeth's crash is not in 3.40.11-win32p, because the location 004791FF is in the middle of an instruction in that version of the executable, and the bytes at EIP are nothing alike whatsoever. Also, Mordeth's crash strongly resembles the 3.40.10 PolyObject save loading crash which was already fixed (by 3.40.11).

Share this post


Link to post

Quasar, how are you such a boss? I didn't know you could load the stack dump into a disassembler, my bad guys. Looks like that stuff is useful after all!

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×