ikelos

Ok, so after discussion today it sounds as though there's development going on to rework the core of this, but I don't want it to hold up the 2.4.0 release....

Current state of this is still pending a review by @atcuno

Thanks for this! There's a few points that I'd suggest doing a different way: * The temporary file to hold the csv looks well done and suitably considered, but having...

Unfortunately the renderer options issue still needs a little more consideration, so I'm afraid there isn't a specific deadline for it getting added, but the issue will be updated when...

That much better, thanks! Unfortunately we're still waiting on getting the renderer options into the tree (due to the filename argument needing to be used), but having this here should...

@JonathanOuellet1275 We don't has a timeline for this pull request. It alters the CLI in a way that's very specific to sql support, which won't extend nicely if we gets...

Thanks for the report, the volatility 2 truecrypt plugin hasn't yet been ported over to volatility 3, but we'll leave this issue open as a way of tracking what plugins...

Hmmm, thanks for the report! This looks like it may be a bit of work. My guess is Microsoft started allowing C++ in their core and up to this point...

Thanks for that, it looks like DIA does some clever name mangling, so what we see as ``, they reconstruct as something like `_IO_RESOURCE_DESCRIPTOR::::` or similar.

Hmmm, I just checked out that branch and ran this command `python volatility3/framework/symbols/windows/pdbconv.py -g c0685fe74deea4bec6f9cc52feac5d231 -p win32k.pdb` which worked without errors and the type is defined [here](https://github.com/volatilityfoundation/volatility3/blob/feature/pdbconv-cplusplus-vs19/volatility3/framework/symbols/windows/pdb.json#L1177), so I'm a...