DRL > Bug Reports

[0.9.9.4] ..An unhalted exception? (Yipe!)

(1/2) > >>

Bloax:
I was just playing as per usual, (with a bit of save-cheating because I suck), just killed the last nasty caco - and...

*Poof*

This appears:

http://i.imgur.com/7QAoj.png

Got any ideas what this may be? (And yes, I do lack the patience to start over 666 times to get later into the game. Though I've only died about once this run. *Phew!*)

Game Hunter:
As an FYI for bug reporters that can provide error.log information, it is standard to simply use code tags and dump the log into the post. For example:


--- Code: -------------------------------------------------------------------------
Timestamp   : 9/9/2011 17:47:04
Error level : CRITICAL
Message     : Player action exception!

Error message : Access violation
----------------------------------------------------------------------

----------------------------------------------------------------------
Timestamp   : 9/9/2011 17:47:07
Error level : FATAL EXCEPTION
Message     : Fatal exception encountered

An unhandled exception occurred at $004810AD :
Exception : cannot resume non-suspended coroutine
  $004810AD  TLUACONFIG__RESUME,  line 107 of d:/Projects/fpcvalkyrie/src/vluaconfig.pas
  $00488609  TPLAYER__AICONTROL,  line 1083 of src/dfplayer.pas
  $0049DE07  TBEING__ACTION,  line 649 of src/dfbeing.pas
  $0049DF6C  TBEING__CALL,  line 675 of src/dfbeing.pas
  $0041E70A  TDOOM__RUN,  line 444 of src/doombase.pas
  $004022CA  main,  line 91 of src/doomrl.pas

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


--- End code ---

This makes it easier not only for readers (since we don't need to hassle with downloading the file) but posters can just copy-paste text from the log here, which should be easier than attaching the file to the post. I'm not picking on you specifically, I've just been seeing a few people do this and wanted to let everyone know how the typical procedure goes.

I KNOW I've seen this kind of error somewhere, but I can't say I have any clue as to what the problem could have been. vluaconfig.pas points to your config files, so there may be some kind of oddity in there if you've been messing with them at all.

Also, welcome to the forums!

Bloax:

--- Quote from: Game Hunter on September 09, 2011, 10:17 ---As an FYI for bug reporters that can provide error.log information, it is standard to simply use code tags and dump the log into the post. For example:


--- Code: ---Stuff
--- End code ---

--- End quote ---
Hm, thanks. Didn't think of that one, since it's rare to have such short error logs. (They're usually 40-something KB.)


--- Quote from: Game Hunter on September 09, 2011, 10:17 ---I KNOW I've seen this kind of error somewhere, but I can't say I have any clue as to what the problem could have been. vluaconfig.pas points to your config files, so there may be some kind of oddity in there if you've been messing with them at all.
--- End quote ---
Well, I doubt it's about my configs. Since the only changes I applied was specifying an AlwaysName and turning on SkipIntro. (Both should only crash the game when starting a new game, not mid-game!)
And thanks for the welcome. :x

Edit: I also seem to have lost my Gatling gun after the crash. A shame. :(

Kornel Kisielewicz:
In case of this error, it's VERY important to remember what KEY you pressed just before the crash... do you remember?

Bloax:
I'm very certain it was PGDN, as I strafed in between some lava. I think there was a lava spot just in the "space" after "An", and as I went through it..
Well, you already know what happened next.

Navigation

[0] Message Index

[#] Next page

Go to full version