I'm not sure if it's me doing something wrong or it's a bug/intentional feature of the new sjASM...

After setting the ouput file size with the pseudo-op OUTPUT, no matters what happened with compilation, success or failure, the specified file is generated. I haven't checked what's in the file; but I guess that it'll be mostly garbage...

Sjasm always writes an output file. It'll contain mostly what you'd expect, except the errors, and address offsets may be wrong.

I also have one problem with sjasm. When generating a symbol file, local labels (with the '_' prefix) aren't part of the symbol file. This pretty much makes the local labels useless when debugging the code using emus that support symbol files.

Me and Vincent have a workaround, a script that pre-processes the assembly files and changes the local labels but thats a quite bad workaround.

(If you changed the behavior in later versions I apologize for the comment, not sure what version we're using)

Labels starting with '_' are not local labels in sjasm0.3 and newer. They should be listed in the symbol file, so I guess you found a bug in sjasm.

There's actually another problem I have experienced for a couple of versions; some code can crash the compiler. I think it has something to do with the includes (no binary includes), but I havn't been able to create a unit test for it.

afaik sjasm crashes when you include a binary file with include instead of incbin.