| View previous topic :: View next topic |
| Author |
Message |
bshi02 Newbie cheater
Reputation: 0
Joined: 08 Apr 2020 Posts: 17
|
Posted: Mon Mar 13, 2023 10:52 pm Post subject: Question about beakpoint in cheat engine. |
|
|
I found an address which seems to cause to pass a day in game(Princess maker3 HD).
So I set a breakpoint on this address(56847B4928)
As soon as Game(Princess maker3 HD) reached breakpoint and it stop executing, So I clicked "step into(F7)"in order to execute a single instruction, But It seems that I could not manipulate CE's debugger anymore.It is the same with the effects of run(F9), not able to execute a single instruction.
I recorded a video like below dropbox link in order to demonstrate this symptom more precisely.
dropbox . com/s/ocyif3q65e05ste/pm3_cheat%20engine.mp4
frankly speaking,Although I am not familiar with assembly language,But I have some experience to make and debug some C language code with codeblocks.
As far as I remember, If I trigger "step into" in succession in codeblocks debugger,It should show the flow of code from the breakpoint.
But It seems that debugger of CE is not able to execute a single instruction from the address of breakpoint.
|
|
| Back to top |
|
 |
++METHOS I post too much
Reputation: 92
Joined: 29 Oct 2010 Posts: 4197
|
Posted: Mon Mar 13, 2023 11:12 pm Post subject: |
|
|
| After checking to see what writes to the address, click 'Stop' in the debugger window before setting a breakpoint in memory viewer. Try that and see if it works.
|
|
| Back to top |
|
 |
bshi02 Newbie cheater
Reputation: 0
Joined: 08 Apr 2020 Posts: 17
|
Posted: Tue Mar 14, 2023 12:03 am Post subject: |
|
|
| ++METHOS wrote: | | After checking to see what writes to the address, click 'Stop' in the debugger window before setting a breakpoint in memory viewer. Try that and see if it works. |
Thank you very much for your reply!
When I click stop button in the viewer(window) of "following opcodes write to XXXX" "Step into" works exactly as I want.
It seems that if a breakpoint is triggered, It would be conflict with another debugger in the viewer(window) of "following opcodes write to XXXX".
|
|
| Back to top |
|
 |
|