search

LimJungYeon / volatility

Automatically exported from code.google.com/p/volatility
GNU General Public License v2.0
0 stars 0 forks source link

Volatility was functioning, now errors out #518

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Any call to volatility. I had it aliased, but even doing 
/usr/share/volatility/vol.py -f $file imageinfo (or --help, or any other 
module) will create this error.
2.
3.

What is the expected output? When I do --help, I expect help, instead I see

Volatility Foundation Volatility Framework 2.4
Traceback (most recent call last):
 File "/usr/share/volatility/vol.py", line 192, in <module> main()
 File "/usr/share/volatility/vol.py", line 148, in main registry.register_global_options(config, addrspace.BaseAddressSpace)
 File "/usr/share/volatility/vol.py", line 157, in register_global_options for m in get_plugin_classes(cls, True).values():
 File "/usr/share/volatility/vol.py",line 152, in get_plugin_classes raise Exception("Object {0} has already been defined by {1}".format(name, plugin))
Exception: Object VirtualBoxCoreDumpElf64 has already been defined by <class 
'volatility.plugins.addrspaces.elfcoredump.VirtualBoxCoreDumpElf64'>

What version of the product are you using? On what operating system?

Looks like 2.4, on Linux "redacted" 3.12-kali1-amd64 #1 SMP Debian 
3.12.6-2kali1 (2014-01-06) x86_64 GNU/Linux

Please provide any additional information below.

I can't possibly think of what's changed, except perhaps me running an apt-get 
update && apt-get upgrade, but something seems to be broken somewhere.

Original issue reported on code.google.com by Arvand...@gmail.com on 5 Nov 2014 at 11:00

GoogleCodeExporter commented 9 years ago 
Please try clearing out all *.pyc files that might have been created in 
/usr/share/volatility, and try rerunning it again (probably a filename changed, 
or got rearranged).

If you're still having problems, please file a new bug on github (which is 
where all development has moved to).  
https://github.com/volatilityfoundation/volatility/issues

Marking as Invalid, since this should be filed on Github now...

Original comment by mike.auty@gmail.com on 6 Nov 2014 at 11:26