Functions

The options below appear when the Edit menu is opened from the Functions View. In other views, the menu adapts dynamically and may show a different set of options.

Below is an overview of all actions that can be accessed from this menu.

UI Action Name	Action Name	Description
Create folder...	DirTreeCreateFolder	Create folder with items
Insert...	DirTreeInsert	Create a structure, union, or enumeration
Delete function(s)...	DirTreeDelete	Delete a type
Edit function...	DirTreeEdit	Open type editor for type
Undo	UndoAction	This command reverts the database to the state before executing the last user action. More…
Redo	RedoAction	This command reverts the previously issued Undo command. More…
Copy	DirTreeCopy	Copy
Copy all	DirTreeCopyAll	Copy all
Unsort	DirTreeUnsort	Unsort
Quick filter	DirTreeQuickFilter	Quick filter
Modify filters...	DirTreeModifyFilters	Modify filters
Reset filters	DirTreeResetFilters	Reset filters

Undo

This command reverts the database to the state before executing the last user action. It is possible to apply Undo multiple times, in this case multiple user actions will be reverted.

Please note the entire database is reverted, including all modifications that were made to the database after executing the user action and including the ones that are not connected to the user action. For example, if a third party plugin modified the database during or after the user action, this modification will be reverted. In theory it is possible to go back in time to the very beginning and revert the database to the state that was present immediately after performing the very first user action. However, in practice the undo buffers overflow because of the changes made by autoanalysis.

Autoanalysis (Options → General... → Analysis) generates copious amounts of undo data. Also, please note that maintaining undo data during autoanalysis slows it down a bit. In practice, it is not a big deal because the limit on the undo data is reached quite quickly (in a matter of minutes). Therefore, if during analysis the user does not perform any actions that modify the database, the undo feature will turn itself off temporarily.

However, if you prefer not to collect undo data at all during the initial autoanalysis, just turn off the UNDO_DURING_AA parameter in ida.cfg.

The configuration file ida.cfg has 2 more undo-related parameters:

Parameter	Description	Default
UNDO_MAXSIZE	Max size of undo buffers. Once this limit is reached, the undo info about the oldest user action will be forgotten.	128MB
UNDO_DEPTH	Max number of user actions to remember. If set to 0, the undo feature will be unavailable.	1000000

Since there is a limit on the size of undo buffers, any action, even the tiniest, may become non-undoable after some time. This is true because the analysis or plugins may continue to modify the database and overflow the buffers. Some massive actions, like deleting a segment, may be non-undoable just because of the sheer amount of undo data they generate.

Please note that Undo does not affect the state of IDC or Python scripts. Script variables will not change their values because of Undo. Also nothing external to the database can be changed: created files will not be deleted, etc.

Some actions cannot be undone. For example, launching a debugger or resuming from a breakpoint cannot be undone.

Redo

This command reverts the previously issued Undo command. It is possible to use Redo multiple times.

This command also reverts all changes that were done to the database after the last Undo command, including the eventual useful modifications made by the autoanalysis. In other words, the entire database is modified to get to the exact state that it had before executing the last Undo command.