For all the asserts, is root cause error in grammar files Or is 
code problem?
All .l & .y files change from original,  so is there a way to check 
these files for problems?  Someone explain better those asserts?

I find this for bison,
To enable compilation of trace facilities, you must define the 
macro YYDEBUG when you compile the parser. You could use `-
DYYDEBUG=1' as a compiler option or you could put `#define YYDEBUG 
1' in the C declarations section of the grammar file (see section 
The C Declarations Section). Alternatively, use the `-t' option 
when you run Bison (see section Invoking Bison). We always define 
YYDEBUG so that debugging is always possible.

The trace facility uses stderr, so you must add #include <stdio.h> 
to the C declarations section unless it is already there. 

But it no produce output on stderr?

here is stderr file,
error   : interpRunScript: jump out of range
error   : interpRunScript: *** ERROR EXIT *** (CurEvent=51)
error   : Original event ID: 67 (of 114)
error   : Current event ID: 51 (of 114)
error   : Call depth : 1
error   : interpRunScript: error while executing a script
error   : Assert in Warzone: \lib\script\interp.c:958 : 
interpRunScript (FALSE), last script event: 'buildTruck'
error   : eventFireCallbackTrigger: event initialisedEvent: code 
failed
error   : Assert in Warzone: \lib\script\event.c:1080 : 
eventFireCallbackTrigger (FALSE), last script event: 'buildTruck'
error   : interpRunScript: jump out of range
error   : interpRunScript: *** ERROR EXIT *** (CurEvent=51)
error   : Original event ID: 67 (of 114)
error   : Current event ID: 51 (of 114)
error   : Call depth : 1
error   : interpRunScript: error while executing a script
error   : Assert in Warzone: \lib\script\interp.c:958 : 
interpRunScript (FALSE), last script event: 'buildTruck'
error   : eventFireCallbackTrigger: event initialisedEvent: code 
failed
error   : Assert in Warzone: \lib\script\event.c:1080 : 
eventFireCallbackTrigger (FALSE), last script event: 'buildTruck'
error   : interpRunScript: jump out of range
error   : interpRunScript: *** ERROR EXIT *** (CurEvent=51)
error   : Original event ID: 67 (of 114)
error   : Current event ID: 51 (of 114)
error   : Call depth : 1
error   : interpRunScript: error while executing a script
error   : Assert in Warzone: \lib\script\interp.c:958 : 
interpRunScript (FALSE), last script event: 'buildTruck'
error   : eventFireCallbackTrigger: event initialisedEvent: code 
failed
error   : Assert in Warzone: \lib\script\event.c:1080 : 
eventFireCallbackTrigger (FALSE), last script event: 'buildTruck'
error   : interpRunScript: jump out of range
error   : interpRunScript: *** ERROR EXIT *** (CurEvent=1)
error   : Original event ID: 1 (of 6)
error   : Current event ID: 1 (of 6)
error   : Call depth : 0
error   : interpRunScript: error while executing a script
error   : Assert in Warzone: \lib\script\interp.c:958 : 
interpRunScript (FALSE), last script event: 'initialisedEventTwo'
error   : eventFireCallbackTrigger: event initialisedEventTwo: code 
failed
error   : Assert in Warzone: \lib\script\event.c:1080 : 
eventFireCallbackTrigger (FALSE), last script event: 
'initialisedEventTwo'
error   : interpRunScript: jump out of range
error   : interpRunScript: *** ERROR EXIT *** (CurEvent=0)
error   : Original event ID: 0 (of 6)
error   : Current event ID: 0 (of 6)
error   : Call depth : 0
error   : interpRunScript: error while executing a script
error   : Assert in Warzone: \lib\script\interp.c:958 : 
interpRunScript (FALSE), last script event: 'initialisedEvent'
error   : eventFireCallbackTrigger: event initialisedEvent: code 
failed
error   : Assert in Warzone: \lib\script\event.c:1080 : 
eventFireCallbackTrigger (FALSE), last script event: 
'initialisedEvent'

--
Protect your investment. Click here to find the homeowner insurance policy that 
you need.
http://tagline.hushmail.com/fc/CAaCXv1QU9B6cL2bKAm8QALOcisTUI4i/





_______________________________________________
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Reply via email to