crash

[darkgod]

A part of me died inside after I got to level 14 and into the Sandworm Lair and then the game stopped working. In my case the screen wouldn't show up properly, it was only showing my desktop inside the program.

did you minimize the window ? do something special ?
On beta1 or 2 ?

[Obsilium]

Beta 2 - expanded the window somewhat on 16x16 ASCI windowed 800x600(I think) to get most of the map to show, which also caused quite a bit of lag. Using Windows XP.

[Shoob]

I just got a crash in the wilderness, hit 92% of lvl 16 and was running up from the OF to the top of the map (just to reset the monsters there) and near the top I went boom, nothing that interesting besides refusing encounters in stdout but you can have it (if you want)...

I guess the game was running slowly too, but meh, it does that occasionally... I will see if I can get this again, if I can I will run gdb too.

[rmeakins]

As a bit of a workaround, I've noticed that if you save your game and then the game crashes, the saved game is not affected so you can reload at your last save point.

You can never save too often CTRL + S is your best friend.

[Shoob]

yeah I know, I have been playing this game since alpha 1 it just is hard to remember to do when your character is nigh invulnerable (I almost have 60 armor now, with only a dwarven steel plate)

[bio_hazard]

Another crash, again in Trollshaws. stderr file is blank. This happened while moving along the edge of the map.

[rmeakins]

I'm fairly sure these crashes do not happen in the linux version. I've just been running beta 2 for a few hours and I can't reproduce a crash. However, in the windows version it usually would take about 20 minutes.

Does anyone know of a way to debug this sort of thing in windows?

[madmonk]

If it is that quick then you might want to download GDB and try that.

[rmeakins]

Cool, downloaded it and trying it out.

For some reason, I'm playing a mage on my Windows PC and it hasn't crashed yet, but my arcane warriors crashed all the time.

[rmeakins]

Hmm just encountered one straight away:

Code: Select all

(gdb) run
Starting program: C:\Games\t-engine4-windows-1.0.0beta2/t-engine.exe
[New Thread 4060.0xfe4]
[New Thread 4060.0xb4]
[New Thread 4060.0xfa8]
[New Thread 4060.0xeac]
[New Thread 4060.0x2a0]
[New Thread 4060.0xf0c]
[New Thread 4060.0xefc]
[New Thread 4060.0xf6c]
[New Thread 4060.0xffc]
[New Thread 4060.0x244]
[New Thread 4060.0xef8]
[New Thread 4060.0xc4]
[New Thread 4060.0x634]

Program received signal SIGSEGV, Segmentation fault.
0x00401a24 in ?? ()
(gdb) info stack
#0  0x00401a24 in ?? ()
#1  0x00401880 in ?? ()
#2  0x8b10245c in ?? ()
#3  0x8920245c in ?? ()
#4  0x8b142474 in ?? ()
#5  0x89242474 in ?? ()
#6  0x8b18247c in ?? ()
#7  0x7c8b2853 in SetConsoleMaximumWindowSize ()
   from C:\WINDOWS\system32\kernel32.dll
#8  0xd2852824 in ?? ()
#9  0x428b1e74 in ?? ()
#10 0x8b0a8b04 in ?? ()
#11 0x0f10245c in ?? ()
Cannot access memory at address 0x891cec87
(gdb)

Hope that helps!

[registeringislame]

TEngine is multithreaded? Colour me impressed.

[darkgod]

Sound is in a different thread, and modules can request new threads too. Like to download things, ...

rmeakins: Humm silly me the windows port is not comiled with debug info, yet this is interresting, keep on doing that see if "SetConsoleMaximumWindowSize" is always there