Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

980 - Compiler Crash!

7 replies · 1,360 views · Started 21 March 2009

Yep, I'm sorry to report that it's still not fixed. when parsing it seems to get to stage 5 of 'operation crash' before, uhh, crashing.

I have no other information than this. :tongue:

EDIT: actually I just want to clarify that it was working for me fine in 979.

EDIT2: My bad. I meant to say parsing '5'. Typo fixed. sorry.

EDIT3: Well I thought it might be due to increasing a function to take 12 arguments so I tried again. This time it died generating object code. yucky.

I have not seen any crashing in 980, so, my technique for isolating compiler crashes:

1. Comment everything out.
2. Does it still crash? (If yes, break. Big problems)
3. Uncomment the individual scripts, one by one.
4. When you get to the one that crashes, go to step 5. Else, go to step 3.
5. Comment out the functions in the script again.
6. Uncomment the functions, one by one.
7. When you get to the one that crashes, go to step 8. Else, go to step 6.
8. Comment the body of that function again.
9. Uncomment each line, one by one.
10. When you get to the one that crashes, create a new file with a script with that line in it.
11. Does the new file crash? (If yes, post a bug!)

This is where compiler directives would be helpful (such as #if x) and / or C++ style comments (/*...*/).

Anyway I haven't had any compiler crashes either and my Zelda II Classic quest uses a lot of scripting. 😊 Please let us know what you find.

Oh yeah, comment everything out one by one, why didn't I think of that...>_> Let me check my date book...ah yes, I believe I have wednesday open to do that. I'll mark it down. :thumbsup: Much easier than posting a thread about it and seeing if anyone else has additional information. 🙄

:\ ..I did comment out and delete various things that might be the most common causes of the crash, but I wasn't able to isolate anything in particular yet.

Weird, I managed to reproduce this bug once, but in the process of trying to diagnose it it just magically disappeared, and I haven't been able to reproduce it since.

When I release a new build check it out.

That is weird. It mysteriously works in build 982. ...or it mysteriously didn't work in 980. You decide. :P