Skip to content
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

Memory Breakpoints #1123

Closed
malexkiy opened this issue Sep 28, 2016 · 14 comments
Closed

Memory Breakpoints #1123

malexkiy opened this issue Sep 28, 2016 · 14 comments
Labels
bug The issue describes a bug. It does not mean the bug has been reproduced by a developer. try this This issue needs to be tried by a developer to see if more information is needed.

Comments

@malexkiy
Copy link

malexkiy commented Sep 28, 2016

Memory Break points don't work in x32 version of program. Tried with the latest version

@mrexodia
Copy link
Member

Please give more details it works fine for me

membp

@mrexodia mrexodia added bug The issue describes a bug. It does not mean the bug has been reproduced by a developer. try this This issue needs to be tried by a developer to see if more information is needed. labels Sep 28, 2016
@malexkiy
Copy link
Author

malexkiy commented Sep 28, 2016

Here the screenshots:
Program continues execute, membp doesn't interrupt it.
1
2
3

@mrexodia
Copy link
Member

What are the page protections and what type of memory breakpoint did you
set?
On Thu, 29 Sep 2016 at 00:03, malexkiy notifications@github.com wrote:

Here the screenshots:
Program continues execute, membp doesn't interrupt it.
[image: 1]
https://cloud.githubusercontent.com/assets/12190704/18934045/53c84712-85e0-11e6-80b4-36532bd441fa.png
[image: 2]
https://cloud.githubusercontent.com/assets/12190704/18934046/53c8cc0a-85e0-11e6-8923-3c452e4480b5.png


You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#1123 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACWCmbwDuKFJ4WOWN4fC9LRza2X9EcBEks5quuRFgaJpZM4KJWlZ
.

@malexkiy
Copy link
Author

malexkiy commented Sep 28, 2016

Well, the page protection is "-R---" , I've set Access breakpoint. Set with commands "bpm, 'addr', 0, r" and "membp 'addr', 0, r". x64dbg works with x64 program without any problems, but x32dbg...
P.s. I'm working on Windows 7 Pro x64

@mrexodia
Copy link
Member

After you set the memory breakpoint, what protection does it show in the
memorial for the page?
On Thu, 29 Sep 2016 at 00:44, malexkiy notifications@github.com wrote:

Well, the page protection is "-R---" , I've set Access breakpoint. Set
with commands "bpm, 'addr', 0, r" and "membp 'addr', 0, r". x64dbg works
with x64 program without any problems, but x32dbg...


You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#1123 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACWCmdUPW93WfsVURh_NdK881mD66PGFks5quu2_gaJpZM4KJWlZ
.

@malexkiy
Copy link
Author

It shows "-R--G"

@mrexodia
Copy link
Member

Memory breakpoint on access appears to not break on execute probably the wrong enum set somewhere.

@mrexodia
Copy link
Member

Okay, the command bpm addr, 0, r would only break on read of the page addr is in. You can now use bpm addr, 0, a and it will break on read+write+execute. The menus now also work this way.

@malexkiy
Copy link
Author

Hmm... But in x64 version the same is working, in x32 problems. I can set memory breakpoint at required address and it'll interrupt the program, when memory at this address will be read.

@malexkiy
Copy link
Author

I can't use such command, as I need to know, when the memory will be read, not written or executed

@mrexodia
Copy link
Member

mrexodia commented Sep 29, 2016

I tested bpm addr, 0, r on both x32 and x64 and they work as expected (break when an address in the page of addr is read). I tested on the import table of x32dbg.exe and x64dbg.exe and it would break on a call dword ptr ds:[api]

@mrexodia mrexodia added try this This issue needs to be tried by a developer to see if more information is needed. and removed try this This issue needs to be tried by a developer to see if more information is needed. labels Sep 29, 2016
@malexkiy
Copy link
Author

Tested with commit 174b845?

@malexkiy
Copy link
Author

Yeah, now it works correctly.
Thanks!

@mrexodia
Copy link
Member

Glad to help 👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue describes a bug. It does not mean the bug has been reproduced by a developer. try this This issue needs to be tried by a developer to see if more information is needed.
Projects
None yet
Development

No branches or pull requests

2 participants