Menu ▾ ▴

#3288 SCUMM: Crash when pressing SPACE (Pause)

Putt-Putt Travels Through Time
closed-fixed
Max Horn
Unknown Crash/Other (1602)
5
2007-07-01
2007-07-01
No

ScummVM 0.11.0svn (Jul 1 2007 08:51:56)
Features compiled in: Vorbis FLAC MP3 zLib MPEG2

assertion "(pause && _pauseLevel >= 0) || (!pause && _pauseLevel)" failed: file "engines/engine.cpp", line 185

I get this assertion with every single PuttPutt game
plus at least Sam&Max and think it affects all of the
SCUMM based games. (Haven't tested all, though)

Just press SPACE to pause the game regardless at which
point of the game you are.

Updated English(US)

AmigaOS4
gcc version 4.0.2 (AmigaOS build 20051012)

Not sure when this happened first, but it can't be
that long. It wasn't there in the 0.10.0 release.

Discussion

  • Max Horn

    Max Horn - 2007-07-01

    Logged In: YES
    user_id=12935
    Originator: NO

    Works fine over here... Hm, I made a related commit a bit ago, but if that commit fixes it, something else is seriously broken on the Amiga (namely, that fix of mine added a check for g_engine being 0. If that value is 0 for you, i.e. if that change fixes the issue, there is a *serious* problem in your version of ScummVM, and all sorts of things should cause problems).

     

  • Anonymous

    Anonymous - 2007-07-01

    Logged In: YES
    user_id=1028770
    Originator: YES

    I'm not sure if i understand you right.
    I just tried a new build from the latest svn and the issue
    is still there, so i *think* my build isn't *that* flawed?

     

  • Max Horn

    Max Horn - 2007-07-01
    • assigned_to: nobody --> fingolfin
    • status: open --> closed-fixed
     

  • Max Horn

    Max Horn - 2007-07-01

    Logged In: YES
    user_id=12935
    Originator: NO

    No, it's not. I think I just found the true cause of the problem and fixed it. Thanks for pointing this out.

    BTW, don't get me wrong, the "flawed build" was not meant to put down the Amiga port or anything -- I just was kind of scared from the thought that what I initially suspected to be the cause for this crash (which does not occur over here), was *really* the cause -- because that would have been pretty bad, there would have been nothing I could have done about that then :-/.

    So I am kinda happy it just was a very stupid mistake on my side which was responsible for this crash, and not yet another compiler bug :-)

    Should the bug still be there with rev 27836, please reopen this item.