Chaosforge Forum

  • August 14, 2022, 19:11
  • Welcome, Guest
Please login or register.



Login with username, password and session length
Pages: [1]

Author Topic: [0.9.9.4] Access Violation crash.  (Read 2397 times)

rekenne

  • Elder
  • First Lieutenant
  • *
  • *
  • Offline Offline
  • Posts: 200
    • View Profile
[0.9.9.4] Access Violation crash.
« on: October 06, 2011, 06:49 »

This *might* be the can't reload using an ammo container that doesn't have enough ammo bug? But I don't know offhand and didn't check. I didn't know that was a known bug before I kept going. Sorry. D:

 Error: Access violation Press <Enter>... Error written to error.log,
 please report! Game saved. Press <Enter> to exit. Press <Enter>...
                     #·\|····#·#·······
                     #·······#·# ·····
                      ·······#·#  0·0
                #+#######/####/####+####
                #•|··/··············}··+
              |·#}···#·#######/#######·#
              %·/···"#·#·············#
              ··#······#············%#
                #····/An unhandled exception occurred at $004810AD :
Exception : cannot resume non-suspended coroutine
  $004810AD  TLUACONFIG__RESUME,  line 107 of d:/Projects/fpcvalkyrie/src/vluaco
nfig.pasly                  Armor : blue armor [2/2] (55%)
  $00488609  TPLAYER__AICONTROL,  line 1083 of src/dfplayer.pas3) [2/5] (P1)
  $0049DE07  TBEING__ACTION,  line 649 of src/dfbeing.pas    Phobos Base  Lev6
  $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

Abnormal program termination! Please write down the above
to help get rid DoomRL of all those bugs! You only need
to write down the filenames and linenumbers.
Attempting to save game.... Press <Enter>
Logged

Game Hunter

  • Programmer
  • Local Inquisitor
  • Lieutenant General
  • *
  • *
  • Offline Offline
  • Posts: 1044
  • Looks like game to me.
    • View Profile
    • Channel, the Roguelike
Re: [0.9.9.4] Access Violation crash.
« Reply #1 on: October 06, 2011, 07:50 »

Please remember to use code tags when posting error.log information, like so:
Code: [Select]
Error: Access violation Press <Enter>... Error written to error.log,
 please report! Game saved. Press <Enter> to exit. Press <Enter>...
                     #·\|····#·#·······
                     #·······#·# ·····
                      ·······#·#  0·0
                #+#######/####/####+####
                #•|··/··············}··+
              |·#}···#·#######/#######·#
              %·/···"#·#·············#
              ··#······#············%#
                #····/An unhandled exception occurred at $004810AD :
Exception : cannot resume non-suspended coroutine
  $004810AD  TLUACONFIG__RESUME,  line 107 of d:/Projects/fpcvalkyrie/src/vluaco
nfig.pasly                  Armor : blue armor [2/2] (55%)
  $00488609  TPLAYER__AICONTROL,  line 1083 of src/dfplayer.pas3) [2/5] (P1)
  $0049DE07  TBEING__ACTION,  line 649 of src/dfbeing.pas    Phobos Base  Lev6
  $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

Abnormal program termination! Please write down the above
to help get rid DoomRL of all those bugs! You only need
to write down the filenames and linenumbers.
Attempting to save game.... Press <Enter>

That being said, this appears to be the same bug as the one in this thread, and probably is, in fact, the shotgun reload bug. If nothing else, the errors point to the same part of the code, so it would be hard to think otherwise.
Logged
I'm just a dude playing a dude disguised as another dude.

Latest LPs: Angband, Delver

tehtmi

  • Programmer
  • Local Inquisitor
  • Lieutenant Colonel
  • *
  • *
  • Offline Offline
  • Posts: 458
    • View Profile
Re: [0.9.9.4] Access Violation crash.
« Reply #2 on: October 06, 2011, 18:27 »

Unfortunately, this error message seems to be a general message that appears for most things in the input handler.  Thus, it helps us a great deal to know what key you pressed right before this error occurred.  I see you have a combat shotgun equipped, so I am indeed inclined to write this up to the full reload bug.
Logged
Pages: [1]