ko1N

I couldnt see any additional steps that memprocfs is doing to initialize leechcore, but there probably is something i overlooked. Otherwise im kinda out of ideas right now, will have...

No one used them before but it should be quite straight forward to add those parameters, do you have an example on how they would be set? I Assume remote...

It seems to only require szRemote to be set: https://github.com/ufrisk/MemProcFS/blob/f1abe87dc2411fc6c097e4a97a8dd94edb6a8e52/vmm/vmmdll_core.c#L604 I gave it a shot and added a `remote` parameter that you should be able to set now. Do you...

I noticed yesterday that more complex argument formatting will confuse our argument parser. For the time being you can parse it manually like so: ``` let args = ConnectorArgs::new(None, "device=pmem,remote=\"rpc://insecuret:hp\"".parse().unwrap(),...

I updated the title but would like to keep this open until the original issues are resolved (and arg parsing works fine).

> I noticed yesterday that more complex argument formatting will confuse our argument parser. For the time being you can parse it manually like so: > > ``` > let...

The error you are seeing comes from a missing physical memory connection. In memflow the examples allow to chain arguments, e.g. you can first load a connector with `-c qemu`...

After some discussion with @h33p we think the best approach would be to rename the `size` field to `max_address` and eventually introduce a `real_size` field which could provide the usable...

I can't reproduce this on linux 6.11.1. Can you confirm this is still an issue on newer kernels?

Currently the C library (LeechCore) does not support building for macOS at all. If you want to send over a PR with a diff/patch that we can apply to that...