ko1N

I think @h33p is working on a new i/o system which should also allow async. I'll assign this issue to him.

Sounds like a great suggestion. I'll have to take a look into how this works.

That seems odd. Does it hang while printing the module list itself? Because memflow isn't involved at this point anymore. `module_list()` will just return the list and you just iterate...

> The error also appears while executing os.module_list() i just recognized:   Alright, im not sure if i understand correctly but the errors you say are not unlikely to...

It's not out of the ordinary that there might be entries that are not fully populated. We do not apply any filtering to the module_list output. You could however simply...

Thanks for the heads up! I reverted to the older procfs version to fix this. However we are waiting for https://github.com/m4b/goblin/pull/386 to properly re-release memflow-native and fix it properly in...

I worked on the new memflowup release in the last couple weeks specifically for binary builds. If you wanna give it a shot, we already have release artifacts for memflow-native...

Hey there, thanks for the issue! I will remove the old tutorial series from the readme as theyre really only valid for 0.1. As a replacement for the old CLI...

Hey there, better place for this issue would be memflow-pcileech project. Anyways, does leechcore require to set the device argument to "vmware://" or is "vmware" sufficient? I personally haven't tried...

Device is straight put into LC_CONFIG: https://github.com/memflow/memflow-pcileech/blob/main/memflow-pcileech/src/lib.rs#L38 Does it need anything else being setup apart from running as admin?