Aria Desires

> Is there a reason for this aside from hiding the implementation details? There's already a few places where we lazily compute/parse a value, and making it a field kinda...

#264 implements the stream As I beef up the processor I have been vaguely mulling this new architectural feature: Introduce a struct in process_state.rs called something like ProcessEnv that variously...

I think I mentioned this elsewhere but tossing it here too: currently "page is writeable/executable" is a fuzzy signal because it is considered best-practice for a JIT to use W^X...

thanks for all the hard work, sorry for the delays!

Oh I was about to close this having not noticed the *system* part. Interesting, but probably one of the last things I'll get around to.

Here's a rough sketch of the tasks that need to be accomplished, without any inherent separation/structure. ```mermaid graph LR; handle-dump parse-dump process-dump walk-thread caller-with-cfi caller-with-fp caller-with-scan line-info-at-addr caller-registers registers-for-thread reg-for-frame...

And here's the current crates: ```mermaid graph LR; subgraph app handle-dump end subgraph minidump parse-dump memory-at-addr mod-at-addr end subgraph minidump-processor process-dump walk-thread registers-for-thread reg-for-frame caller-registers caller-with-scan caller-with-fp caller-with-cfi end subgraph...

Note that these graphs currently lie a bit, in that "symbols" never asks for `mod-at-addr`, "minidump-processor" does, and passes that in. Currently "symbols" has no awareness of "minidump" and entirely...

Also note that coupling `parse-symbols` with `load-symbols-for-mod` allows us to do async/streaming parsing of the symbol file as it downloads, reducing latency (a bit) and peak memory usage (by 50%)....

If there's some macro or whatever to get the version from the Cargo.toml, perhaps the "post release" commit should update everything to NEXT_VERSION-alpha. e.g. the tree looks like: * some_random_commit:...