eventFireCallbackTrigger: script interpreter is already running

[tbyte]

Warzone2100 Version
Warzone 2100 - Version 2.0.4 - Built Aug 29 2006 - DEBUG

Operating System
FreeBSD WarHeaD.OTEL.net 6.1-STABLE FreeBSD 6.1-STABLE #0: Tue Aug 22 01:57:28 EEST 2006    [email protected]:/usr/obj/usr/src6/sys/WARHEAD  i386

Hardware Information
nVidia GF6800GT (nVidia binary drivers) Athlon64 3700+ 2G RAM Dual-Channel DDR400

Warzone2100 Configuration
Default - I've rm -rf ~/.warzone2100

Bug Description
  When I start a new game and when the first intelignece report comes this happens:

error:      interpRunScript: bInterpRunning = TRUE
error:      interpRunScript: bInterpRunning = FALSE - 1639225130
error:      interpRunScript: bInterpRunning = TRUE
error:      eventFireCallbackTrigger: script interpreter is already running
error:      Assert in Warzone: event.c:977 : eventFireCallbackTrigger (FALSE)
Assertion failed: ((0)), function eventFireCallbackTrigger, file event.c, line 977.

(first 3 lines are from mine debug info lines - the number is just a rand() so I can see that its realy firing coz the console fills up quickly)

If I comment if (interpProcessorActive()) ... so no check is done the game somehow works
But if I try 'fastplay' it abort()s around interp.c:236 when it checks 'if (bInterpRunning)'.

At that moment I decided to contact You coz I saw that you have made changes to scripting engine and you could figure out what's happening more quickly

[Kamaze]

1. Read the Bugreporting-Readme. (Reporting Template)
2. Change your post to fit it.
3. Wait for replys again

[tbyte]

LOL I could bet you are deutcsh - Everything should be OK now I think

[Kamaze]

Niki reported the same thing, in the Troubleshooting-Forums.

Can you attach the whole debug logfile?
Niki, if you read this, you too?

For debugging read "Command Line Options".
(Documentation leaks a bit, i think Devurandom or Per will say what the "FLAGS" are...)


//OT: Yes, i am ???  Look into my profile...

[tbyte]

Is it these (debug flags):

static const char *code_part_names[] = {
  "all", "main", "sound", "video", "wz", "3d", "texture",
  "net", "memory", "error", "never", "script", "last"
};

I don't want to sound rude but I know how to find out what command line options are
I'm a programer for almost 15 years now

I'll try to run it with --debug script to see what happens.

//OT: Yes, i am Huh  Look into my profile...

That was the second thing that I've done after I put my bet

[tbyte]

Here is "script" debug:

$:> warzone2100 --debug script
fcntl: Device not configured
script:    allocated space for 27 events
script:    allocated space for 12 events
script:    allocated space for 2 events
error:      eventFireCallbackTrigger: script interpreter is already running
error:      Assert in Warzone: event.c:977 : eventFireCallbackTrigger (FALSE)
Assertion failed: ((0)), function eventFireCallbackTrigger, file event.c, line 977.
Abort trap: 6 (core dumped)

I can provide and backtrace if needed.

[Kamaze]

Hm,... wait for a reply from Devurandom or per...

[DevUrandom]

I commited a quick fix (r304). This probably needs to be revised by Troman to see if we need to (and can) call something similar eventFireCallbackTrigger((TRIGGER_TYPE)CALL_VIDEO_QUIT); (which can't be called here).

[tbyte]

I'll fetch it and will test it tonite. It was showstopper for the FreeBSD port of 2.0.4
Thanks for the quick response.

PS: I hope the changes after the release won't be a poblem for creating a patch against 2.0.4's revisions

[DevUrandom]

Can you already say when a bugfixed version will come out?

Sorry, not yet. But as we figured quite a lot issues after the release I think it won't take that long.

I hope the changes after the release won't be a poblem for creating a patch against 2.0.4's revisions

I am not sure about that.
I hope we have time to fix all those bugs and release a 2.0.5 "soon". (Before 2.1 )

[tbyte]

It worked (atleast on FreeBSD5 at work - I'll test it on 6 tonite at home).

Here are the patches that I extracted( forum didn't allowed me to attach them):



//Edit (kamaze): Did it have the extension ".patch"? I added it as .txt


They were 2 files (it should work as one too) , with '.c' extension because they are prepared for FreeBSD ports and I was too lazy to merge them in a '.txt' file Thanks.

[Kamaze]

I think this is solved.

--> Fixed Bugs