Apologies if this has already been mentioned, but i encounter problems with WinDbg & TD32 debuggers when i place an INT 3 break exception in my code somewhere.
For some reason, the debugger does not parse the opcodes that follow properly & then ends up executing some invalid instruction & crashing.

MASM & TASM seem to use 0CCH opcode, whereas FASM uses CD03H
I know, it is more of a debugger error, but i can't see TD32 being updated anytime soon.

Any chance updating the assembler to use 0CCH opcode in future instead of current CD03H?

OK..sorry, just read a post about this.
I was just used to using INT 3, but i now see how i can use INT3.
So, no problem!