Closed koromodako closed 5 years ago
You're not the first person to have run into this, and I now have a sample where I can recreate the problem, so I'll look into it and see if I can resolve the issue. If the solution is a little complex then it may have to go through our pull request approval policy, but I'll keep this issued updated as I figure out what's what... 5:)
Right, so it turned out this was an issue with the ELF layer I hastily threw together. The offsets for the segments were volatility objects (which therefore carried references to their context with them), and something about that meant it couldn't be marshalled/unmarshalled correctly (needed for context.clone()
and also for pickling). So instead, the segments are now converted to plain old boring ints (rather than spangly volatility ints) and that should have resolved the problem. If you can update the elf64 branch and test it, then I should be able to close this one off... 5:)
Ok, independent verification says that this is now resolved. Do feel free to reopen it if the issue persists for you though! 5:)
Forgot to mention, fixed by commit 94dad4cfc19a3d90d252ca94b7ed83a6b1604878
.
First of all, do not hesitate to rename this issue. It's always hard to find something precise enough without being too long.
windows.pslist
plugin is raising TypeError when analyzing a memory dump (elf64
format). This issue might be related to #97.