Getting some errors in debug.py

[GoogleCodeExporter]

Hey guys, 

I am seeing errors in the current 1.4 branch:

$ python volatility.py 
Volatile Systems Volatility Framework 1.4_rc1
Traceback (most recent call last):
  File "volatility.py", line 126, in <module>
    main()
  File "volatility.py", line 103, in main
    debug.error("You must specify something to do (try -h)")
  File "/Users/mike/Desktop/Volatility-1.4_rc1/volatility/debug.py", line 58, in error
    log(msg, logging.ERROR)
  File "/Users/mike/Desktop/Volatility-1.4_rc1/volatility/debug.py", line 73, in log
    modname = mod.__name__

Original issue reported on code.google.com by michael.hale@gmail.com on 2 Dec 2010 at 10:37

[GoogleCodeExporter]

Hmmmm, that trace is missing the exception, so it's unclear what's causing the 
problem (or which exception to catch in the try/except clause).  Could you 
please provide the remainder of the trace?

The error message (debug.error) suggests it's caused by just running volatility 
without any options, but I can't recreate this problem on either python 2.7 or 
2.6, so it's not clear what differs between our setups.  Could you also check 
this without any additional plugins (just the core ones) please, just in case 
they're causing the problem?

Original comment by mike.auty@gmail.com on 3 Dec 2010 at 12:59

[GoogleCodeExporter]

Hey sorry about that...the only line missing from the output was:

AttributeError: 'NoneType' object has no attribute '__name__'

I checked out a clean r557 and am not getting any errors, even with all 
additional plugins installed. So I don't know what caused my issue, maybe some 
files I had that were old/out of sync. Feel free to close.

Original comment by michael.hale@gmail.com on 3 Dec 2010 at 6:41

[GoogleCodeExporter]

Heheheh, ok, cool.  Do reopen this if you hit the problem again...  5:)

Original comment by mike.auty@gmail.com on 3 Dec 2010 at 11:35

• Changed state: Invalid