ikelos

I've moved this to the `dwarf2json` project, because it doesn't seem to be a voliatlity issue. If the `module.dwarf` file is an ELF (as reported by `file module.dwarf`) then you...

Hi Gus, yep, I totally agree with what you've said but I'm pretty sure we've had people generating ISF files from the wrong type of kernel or something and so...

Just a very simple status line about the generated file that tells you the number of base types, types, symbols and enums would be really helpful to tell whether the...

@0x1abin This issue has been open over a year, but there doesn't appear to have been much progress. The m5stack modules and similar are frozen, so even trying to extract...

I think I'd prefer you to revert them, just so I can do it through the github UI easily, if that's ok? I'm ok with all the ones except the...

Lemme know if you're happy for this to be merged as is, or if you want to throw in the fix for maximum_size/maximum_address?

> Ok, reverted those commits and redid it using the `preferred_filename` as you suggested. See example below. It was a bit tricky as `preferred_filename` has a setter. The file has...

> I think I found the fix here. I disabled Virtualization in my BIOS and re-generated the memory dump and bam, this error went away and I was able to...

Ok, I see. Unfortunately that error message can have a number of reasons because it's very difficult to determine the exact cause. Volatility has a number of heuristics designed to...

This is an identical response to the one you posted to both #1223 and #1139. I don't believe that turning off intel VT-d support will help with all symbol/pdb problems,...