Thank you very much for this dump. Now I can reproduce this bug. In fact there are some bugs.
1 Objects don't clean properly after the script finish. If script uses callbacks ( breakpoint or eventHandler ) they continue to work. If script run as local ( by default ), after its finish the interpreter is deleted and and any attempt to call a callback will lead to a crash.
This script will crash windbg on the next module load:
If you need to use eventHandler, use pykd bootstarpper 1.0 and run script with 'global' options. I try to fix bootstrapper 2.0 ASAP.
Thank you very much for your report again!!!
1 Objects don't clean properly after the script finish. If script uses callbacks ( breakpoint or eventHandler ) they continue to work. If script run as local ( by default ), after its finish the interpreter is deleted and and any attempt to call a callback will lead to a crash.
This script will crash windbg on the next module load:
import pykd
class handler(pykd.eventHandler):
def onLoadModule(self, modBase, name):
"""Load module handler"""
print name
eh = handler()
This script will work normal:import pykd
class handler(pykd.eventHandler):
def onLoadModule(self, modBase, name):
"""Load module handler"""
print name
eh = handler()
del eh
2 The pykd bootstrapper 2.0 crashes on any call of callbacks after script finish.If you need to use eventHandler, use pykd bootstarpper 1.0 and run script with 'global' options. I try to fix bootstrapper 2.0 ASAP.
Thank you very much for your report again!!!