Is there a way to symbolically debug fasm compiled exe's?

For x86 symbolic debugging I do the following all the time:

If you are using Ollydbg for a debugger (currently I am using version 1.10) you can add the symbolic names to the export section that will then show up in the code and variable sections of the debugger. These will also show up in the names lookup popup window.

Be sure to alphabetize all the symbol names in the list in ASCII order, or some of them may not show up in the debugger. The list ordering is case sensitive.

Make an export section that contains all the symbolic names you want to see in your exe debugging session (labels and variables) using the form:

section '.export' export readable writeable

export 'filename.exe',\
label1 ,'label1:',\
label2 ,'label2:',\
var1 ,'var1',\
var2 ,'var2'

The text of 'filename.exe' must exactly match the name of the file being debugged including the extension.

The text inside the quotes behind the symbol names can be whatever you want to be displayed in debugger, so if they are not the same as the name in the code it is up to you to remember what is what.

If you want to debug local labels (not local variables) then use the form:

prev_global_label.local_label ,'prev_global_label.local_label:',\

since local labels (the ones beginning with 1 dot) are always pinned to the previous global label (..globals do not count). I use the ':' in the label text to help me see what are label names vs. variable names in the names lookup.

Local variables cannot be designated or symbolically debugged using this method

After debugging is completed all you have to do is remove the export section symbol names (or the whole export section) and then recompile again to remove the symbolic names from the exe.

I do not know if this works with other debuggers than Ollydbg,