-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example 14 in the tutorial no longer works #21
Comments
Hi, any info about this? Thanks for your help |
Hi, The watch_buffer method does not have a return value - it will always return None, that's normal. As for the reason why the access callback is never called, I'll try reproducing the problem on my side and get back to you. Thanks for the very detailed bug report! I appreciate that :) |
PS: sorry for the late reply, I seem to be always busy lately :( |
Thanks for your answer,
Ok, but this page says it should return a "Buffer Watch Identifier" : http://winappdbg.sourceforge.net/doc/v1.5/reference/winappdbg.breakpoint._BreakpointContainer-class.html#watch_buffer |
Oops, that should not be there. The buffer watch identifier thing was meant to be internally used only. I'll fix the docs... It was never actually returned by that method, as you can see in the sources: http://winappdbg.sourceforge.net/doc/v1.5/reference/winappdbg.breakpoint-pysrc.html#_BreakpointContainer.watch_buffer |
Hi,
"Example #14: watching a buffer" from http://winappdbg.readthedocs.io/en/latest/Debugging.html doesn't work as expected. Entry/Leave callbacks are correctly called when "ReadFile" is called, however, the read buffer is not watched (the access callback is never called).
I modified the script to print the return value of watch_buffer. It always returns None:
My setup:
The text was updated successfully, but these errors were encountered: