Large debug scripts crash pawndisasm about compiler HOT 10 CLOSED

Fixed this in 8383e5b.

from compiler.

Sorry, but it's not fixed. Just downloaded the latest source, cmaked it and compiled pawndisasm with VS2010.
It still crashes immediately on Windows 8.1. Maybe it's something specific to my script?

from compiler.

OK, I guess it's a different bug then. Can you run it under the debugger and see where it's crashing?

from compiler.

Recompiled it with debug symbols and ran
ollydbg pawdisasm.exe myscript.amx

It crashes there
http://puu.sh/dDxgx/c8ac11e9b5.png

Does that help you?

from compiler.

OK, dumped you the entire function http://pastebin.com/i2asXJx6
Crash address appears to be 0x86330D

from compiler.

Thanks, I can kind of spot where it crashed but I'm afraid that's not enough to fix this. Could you make a crashdump (with Debug build)? You can PM me on the forums if you don't want to post the link here.

from compiler.

Like Taskmanger->Process->Create dump file ?

from compiler.

I had a look at the dumps, and it seems like they were captured during normal execution of pawndisasm as there's no exception record in there.

You said you have Visual Studio 2010 - you can just run pawndisasm in it (with your script as the argument) and once it crashes go to the Debug menu -> Save Dump As.I guess OllyDbg can do this too but I haven't used it much.

from compiler.

No problem, send you another one done in VS2013.

from compiler.

I just downloaded the 3.3.3875 pawn source and compiled pawndisasm.c myself. It does not crash while disassembling my gamemode. But there is something strange, the address output from profiler plugin (unknown@0bbfa686) does not exist in the disassembled file. Maybe there's another bug in profiler?

from compiler.