Mason Reed

A good idea would be to watch for [new memflow versions](https://crates.io/crates/memflow/versions) and check if it compiles and passes the [tests](https://github.com/memflow/memflow-py/tree/master/tests) (ONLY WITH [LATEST TAG](https://github.com/memflow/memflow-py/releases/latest)). If it passes, then we should...

When a breaking change occurs the minimum version of memflow will get bumped up. [The first workflow](https://github.com/memflow/memflow-py/issues/7#issue-1501747029) should adhere to this minimum version ([specified in the Cargo.toml](https://github.com/memflow/memflow-py/blob/1fc9d3d4133aff4a91bbb159df616ae712c7dd2a/Cargo.toml#L22)).

Should be noted we prefer one over the other right now, we should use the native byte order of the system for the default `Structure`.

> In process.rs there is a comment starting on line 259 stating that Process.address() returns the address of the PEB. Upon testing, I found that it actually is the address...

2 Is also fundamentally indescribable from our current calling convention API, we should identify structure/memory returns as described by the ABI and add the hidden return argument. In the case...

Preliminary support added with: https://github.com/memflow/memflow-py/commit/e76e46e050a9d333227897dd7add41513da98b92. Once we move to [deduplicate our memory read/write functions](https://github.com/memflow/memflow-py/issues/10), broad support for these null terminated string readers will be added.

For specific embedded architectures and firmware the assignments to specific global registers would also be a very good indicator that the function is the entry point. Take for example in...

Found something promising! https://github.com/trolldbois/ctypeslib I will give it a try and report back.

Typically, I wait for a crates.io release, due to it being a "non-moving" target. However if you would like to you can fork this and swap the version [here](https://github.com/memflow/memflow-py/blob/f6aa0b089ee792887ccdac082cbf8534fc7bac1c/Cargo.toml#L22), then...