Make sense of verbose notifier
VerboseNotifier update
Verbose Notifier

updated to reflect @l1berty requests
Merge pull request #18 from cmaruti/cm_verbose_notifier

Minor update on VerboseNotifier
added op as a class variable. Its set in runFunction but not initialized by the class. There is a race triggered by some binaries (have the md5s) when emulating certain paths functions relying on op existing specifically getRegister in Amd64WorkspaceEmulator check for the variable before its set by runFunction
added check on the class variable op in base class WorkspaceEmulator to make sure its not None before continuing
Merge pull request #21 from vivisect/rp_amd64_fixes

Rp amd64 fixes
Viv memcanvas starts at a valid VA, fixing a lot of render bugs.
the existing code arbitrarily slams in some offset from the va we want
as the starting va.  for viv, if that is in the middle of a string, the
size of the string gets slammed in, causing all offsets to be wrong.  if
a long string exists just prior to the thing you want to see, often your
object doesn't get rendered.
Merge pull request #22 from atlas0fd00m/real-master

Viv memcanvas starts at a valid VA, fixing a lot of render bugs.
Viv Gui: if setting comment or name and current one exists, prepopulate the dialog box with the current one for editing.
Merge pull request #29 from atlas0fd00m/atlas_EasyEditNameAndComment

Viv Gui: if setting comment or name and current one exists, prepopulate ...