Since the release of 1.67.29 version, fasm contains the symbolic information generator, which you can activate with the "-s" switch (followed by the name of the file, where you want the symbolic information to be dumped). For example: should generate (upon the successfull assembly) the symbolic information and write it into TEST.FAS file.

The symbolic information file is provided in a format specific to flat assembler - the main reason behind it is that this way no information would be lost due to conversion into some other format, and also that it keeps the generator relatively simple, while the conversion into some more useful formats (like listing, map of symbols, or debug info) can be done with some external tools.

With the official fasm packages there are provided (in source form) three simple tools, that extract various kinds of information from the symbolic information dump and process it into human-readable text. They provide the listing, preprocessed source dump and symbols dump.
If there are some important changes or new features implemented in those tools, I'm going to post info about into this thread.

Other tools - according to the plan - are to be written not necessarily by me, therefore I'm attaching here the documentation draft for fasm's symbolic information format. When there are any new tools created, they are also should be linked to from this thread.

Documentation of fasm's symbolic information file format

Here comes the list of the existing tools converting "fas" into some other formats (moderators, please feel free to edit this list anytime, when some new tools arrive):

• Tool that generates debug info in CodeView format in COFF object files generated by fasm:
  http://board.flatassembler.net/topic.php?p=89369
  
• Linux program that dumps in text form the contents of "fas" file generated for the ELF binary:
  http://board.flatassembler.net/topic.php?t=10029
  
• Plugin for OllyDbg that loads debug info from .fas file:
  http://board.flatassembler.net/topic.php?p=114370
  
• IDA script which adds FASM debug info:
  http://board.flatassembler.net/topic.php?p=118458
  
• fasolly: yet another plugin which imports .fas into OllyDbg
  http://board.flatassembler.net/topic.php?t=12365
  
• x64dbg plugin
  https://board.flatassembler.net/topic.php?t=20753
  

Tomasz, tell to me that from itself represents fasm debug info? It's native representation of code for fasm.exe or it's hand-collected info. In second case we should change fasm debug info. Because label "las:" and code " labeltoo: mov eax,eax" look equally.

I'm parsed assembly dump and if symbol size not null I use this symbol. But, size of "notlol db "sdkfjs" is not null, too. OK, I'm search the this symbol in symbol table and skip if find. But, code "lab: mov eax,eax" present in sym table. I search ":" in symbol name, but it's bad idea, is't?
How about some flags for label, code,data?

I'm try add line info into pdb files. As base I'm use DigitalMars D codeview converter (cv2pdb). Time spent for understanding fas format is too big! Can you tell me the right algo for this problem?

Sorry, my english is terrible

there is something a little constraining with "build symbols" in fasmw ide, it force to use comand line just to obtain a .lst file.

[REQUEST]
instead of "build symbols" button, it would be smarter to have a "build listing" button, and then, obtain a .lst file, directlly opened in the ide as a text file.
[/REQUEST]

it makes me think about something, what is the .ash extension for?

After I release FASMW with plugin system you are certainly going to have a sample plugin that makes listing.

there really is no simple way to determine boundaries of some data in the assembly language. For example this definition: can be completely legally rewritten as:
and only programmer knows where some functional block starts and where it ends. It is even possible that the same block has many different functions and multiple labels associated, and you can have some code in the middle of the data, or data that is some code at the same time, etc. etc.

That's exactly the reason why I decided that debug info formats that were designed with higher level languages in mind are useless for the case of fasm, and that's why I designed the .fas format to contain all the fasm-specific information.

It contains about as much information as you can get, however it may be sometimes difficult to dig up some relations. See the examples in TOOLS directory of fasm's package.

It's very difficult read this examples, without comments. I'am trace listing.exe for some reasons. Someone instructions enter into a stupor.



- label foo ->size of code 0, skipped
- db 'bar' ->present in sym table (I hope),skipped
- anonymous symbol/label, skiped (I hope it present is sym table)
- same

It is a pity, but the assumptions I can check up only houses.

There are no symbols in those lines, therefore they have nothing to do with symbol table. However you will find all the necessary data about them in the line offsets table (both the output file offsets and the run-time addresses for each line), called "assembly dump" in the documentation.

My plugin for edb-debugger. Sorry, this is not submodule.
https://github.com/darkprof83/edb-debugger/tree/FasLoader

darkprof


How using this ?
whear is dll or exe files ?

xFasImport - plugin for importing debugging information from fasm assembler (from .fas file) into x64dbg debugger:
https://board.flatassembler.net/topic.php?t=22388