Justas Dabrila

The use case here is python3 bindings for the `scanmem.h` API. The inconsistent `globals_t *` usage was a pain which led me to mostly support APIs that take a `globals_t...

Just pushed a commit that adds `scan_in_progress` to `globals_t`. Here is the summary: * `sm_reset` will return false and log using `show_info`. * `handler__set` `sm_searchregions` and `sm_checkmatches` will set `scan_in_progress`...

Here are my thoughts regarding the API. ## Rename globals_t `globals_t` is a bit vague and might cause name collisions. Something along the lines of`sm_globals_t` would be a better fit...

### Ptrace > The standalone functions can be called whenever you like. `read_array` `write_array` and `setaddr` are fine as they are. ### Commands I don't see why the commands API...

> This looks pretty complex. What use case do you have in mind for which setting a log level and an output FILE* wouldn't be enough? Logging to different streams/locations...