ikelos

If we produce a workaround that's wrong, then we have potentially a whole bunch of seemingly complete symbol tables, that won't have the right types and structures in, which will...

A single capture of an `InvalidAddressException` is kinda what we have (see the CLI exception handling code), we just can't recover from it without knowing that it was ok, so...

It successfully found the intel layer: ``` DEBUG volatility3.framework.automagic.stacker: Stacked layers: ['IntelLayer', 'FileLayer'] ``` But is having trouble finding windows in that virtual layer. It's difficult to diagnose it much...

Oh, I missed that, I thought it was all part of the same struct. Yeah, it will be tricky, but otherwise we need to be really careful about changes (even...

If you can get a PR in place for what you're after we can get those tweaked.

Capstone *is* already in [requirements.txt](https://github.com/volatilityfoundation/volatility3/blob/62aa9c1e12841fd2c2aa7180a489f4b8bdab7e51/requirements.txt#L12), but needs to be added to `test/requirements-testing.txt` as part of the PR please. It also indicates that the error checking isn't working, because volatility should...

@atcuno, can you please add capstone to the `test/requirements-testing.txt` as part of this PR so we can get this merged please?

Where are we with this? Is it still draft, or ready for review? Happy for either, just interested in an update so it doesn't get forgotten accidentally...

I hate to say it, but this is a new feature ("support recent kernels") rather than a fix for something that currently works incorrectly, and I don't think it's enough...

It's not a parity release issue since I'm pretty sure volatility 2 will not handle this case.