Tag / Global Comment chunk

[emesare]

Might be useful to associate tags and comments in the address space instead of on the analysis objects themselves, since they might go away or not exist in the first place.

[emesare]

Separate from being referenced via an address space we should also try and store tags in functions.

I wonder if we could just add a tag prefix to comments to denote them.

[utkonos]

@emesare yes, there are a few nuances with comments and tags and for WARP including all of them would be great.

Tags

1. Function tag (attached to the function without a specific address; displayed on the function's signature at the top)
2. Function address tag (attached to a particular address in a function)
3. Data address tag (attached anywhere in a binary view to a particular address)

Comments

1. Function comment (same as function tag; displayed above the function in the various views).
2. Function address comment (same as tag, but a comment)
3. Data address comment (same paradigm as tags, but a comment).

And only one of the three comment types can be modified using the GUI right click. The other kinds of comments have to be changed using Python API. I don't think I'm using the exact same terminology from the API documentation btw, but how I have termed them helped me differentiate between them all. I'm working on implementing read/write of all the ones that are appropriate for the x64dbg plugin.

x64dbg/x64dbgbinja#9

x64dbg/x64dbgbinja#10

[utkonos]

BTW: the real nuance with data address tags and comments is to cross reference them with whether the address is inside a function or not. WARP only wants data address tags and comments to be slurped into a WARP sig if those addresses are inside the function being transmitted via WARP in the first place.