| jessekornblum ( @ 2009-02-14 11:06:00 |
| Entry tags: | hacking, memory analysis |
Fixing the 'suspicious.py' Volatility module
Several people have asked about the following error when using the suspicious.py plugin for Volatility:
Traceback (most recent call last): File "volatility", line 219, inmain() File "volatility", line 201, in main MemoryRegistry.Init() File "/Users/jessek/Volatility-1.3_Beta/forensics/registry.py", line 269, in Init OBJECT_CLASSES = VolatilityObjectRegistry(object2.Object) File "/Users/jessek/Volatility-1.3_Beta/forensics/registry.py", line 244, in __init__ raise Exception("Object %s has already been defined by %s" % (obj,self.objects[obj])) Exception: Object _EPROCESS has already been defined by class 'example3._eprocess'="'example3._EPROCESS'">
The error is caused by a collision of the _EPROCESS object in suspicious.py and example3.py. The easiest way to solve the problem is to remove example3.py from the memory_plugins directory.