Improve manual loading of WARP signature files

[emesare]

What is the feature you'd like to have?
Right now WARP signature files are really expected to be located within the respective load directories, with the manual load command being an afterthought and primarily used to debug. We should improve the process in two ways:

1. Make a single command that loads a signature file and then runs the matcher with just that signature file. This is what people actually want, if you have version 1 of a binary and then a second version of the same binary your tolerance for bad matches is much lower than if your binary was not related at all.
2. Provide a user interface for introspection of the in memory data set. This would allow users to verify that their dataset is loaded correctly, specifically when it comes to the cache flushing that occurs on certain commands.

[utkonos]

Moving my thoughts over here from the other issue.

I have a set of files marked up by SigKit. I tried "Load Signature File" (ignore what is highlighted in the screenshot, the highlight changes just before the screenshot captures the image).

But nothing at all happens. None of the signatures are applied to any functions and the tag type for WARP is not added.

Is this expected behavior?

The logs show this:

[WARP] Loading signature file with 103 functions and 30 types...

[emesare]

The workflow for loading a signature file (as hinted at by improvement number 1) is two steps.

1. Load Signature File
   This will load the signature file into the cache. You can verify that is the case with "WARP\Debug\Cache".

2. Run Matcher
   This will use the signature cache to match on the current view.

This is clearly not what people want. People just want to load a signature file and run the matcher on just those signatures.

If this does not work for you please let me know!

In the short term we should add documentation, and a link to this GitHub issue to the user documentation.