5 ms·
At the risk of stating the obvious - tracing in itself is not that useful, unless you are after just the aggregated stats. To use traces for reversing the API/I
by apankrat 10y ago
At the risk of stating the obvious - tracing in itself is not that useful, unless you are after just the aggregated stats. To use traces for reversing the API/IOCTLs, it's equally (if not more) important to have a good UI for filtering, analysis and cross-correlation.
There's another tool that fills this particular niche quite well [1] and having used it to reverse HP Smart Array drivers among other things I can't recommend it highly enough.
Just 2c.
[1] http://www.rohitab.com/apimonitor http://www.rohitab.com/apimonitor
- deleted 10y ago[deleted]
- grok2 10y agoTook a look at the API Monitor app you recommended -- it is interesting -- can it be used as a procmon replacement in your experience? The UI seems to be a bit better (more intuitively) organized...with procmon, between one instance of running it and another, I always have to search for where the menu settings are to do some action -- it's almost like a GUI over a command line program.
- trentnelson 10y agoJust looked at the apimonitor; kinda' shocked at a) how I've never come across it before, and b) how thorough it is. Very neat, thanks.