Produce output files
Last updated
Was this helpful?
IDA 9.0
Last updated
Was this helpful?
This submenu allows you to produce various output files. It also allows you to unload the database.
The text file-producing operations below will make use of
for output files.
Please enter a file name for the map. IDA will write the following information about this file:
You can use this map file for your information, and also for debugging (for example, Periscope from Periscope Company or Borland's Turbo Debugger can read this file).
Please enter a file name for the assembler text file. IDA will write the disassembled text to this file.
If some I/O problem (e.g. disk full) occurs during writing to the file, IDA will stop and a partial file will be created.
Please enter a file name for the assembler include file. IDA will write the information about the defined types (structures and enums) to this file.
If some I/O problem (e.g. disk full) occurs during writing to the file, IDA will stop and a partial file will be created.
Enter a file name for the assembler listing file. IDA will write the disassembled text to this file.
If some I/O problem (e.g. disk full) occurs during writing to the file, IDA will stop and a partial file will be created.
IDA produces executable files only for:
EXE files: Output files will have the same EXE-header and relocation table as the input file. IDA will fill unused ranges of the EXE file (e.g. between relocation table and loadable pages) with zeroes.
This command will prompt you for a filename and then will create a plain text difference file of the following format:
Please enter a file name for the HTML file. IDA will write the disassembled text to this file.
If some I/O problem (e.g. disk full) occurs during writing to the file, IDA will stop and a partial file will be created.
This command is available only in the graphical version of IDA.
This command creates a GDL (graph description file) with the flow chart of the current function.
If there is an active selection, its flow chart will be generated.
IDA will ask for the output file name. Regardless of the specified extension, the .GDL extension will be used.
This command creates a GDL (graph description file) with the graph of the function calls.
IDA will ask for the output file name. Regardless of the specified extension, the .GDL extension will be used.
This command saves current IDA database into a text file.
You can use it as a safety command:
This command is used when you want to switch to a new version of IDA. Usually each new version of IDA has its own database format. To create a new format database, you need:
Please note that this command does not save everything to text file. Any information about the local variables will be lost!
This command saves all definitions in the local types window into a C header file.
This command saves information about the user-defined types from the IDA database into a text file.
Information about enums, structure types and other user-defined types is saved in a text form as an IDC program.
You can use this command to migrate the type definitions from one database to another.
You may disable the generation of the segmentation information. You may also enable or disable names in the output file.
If you have selected a range on the screen using command, IDA will write only the selected range (from the current address to the anchor).
If you've selected a range on the screen using command, IDA will write only the selected range (from the current address to the anchor).
Enter a file name for the new executable file. Usually this command is used after patching (see commands and ) to obtain a patched version of the file.
For other file formats please create a file.
Only commands affect the executable file contents, other commands (including ) will not affect the content of the disassembled file.
See also submenu.
See also submenu.
If you've selected a range on the screen using command, IDA will write only the selected range (from the current address to the anchor).
See also commands.