0

Screenshot of the breakpoint options

Look at the condition. It is supposed to break only when the R2 is 40, but it breaks in any call to this instruction. I'm using IDA Pro 7.2.181105, debugging with Remote GDB Debugger, an ARMv4T code. I'm completely beginner with IDA Pro.

2
  • I got the same problem. Did you find a solution?
    – NotBigDeal
    Jan 26 at 0:27
  • Sorry friend, I did no found. Upvote the question so maybe someone answer it on the future. I give up on this project. Now instead I use GHIDRA btw.
    – Moonslate
    Feb 12 at 2:36

1 Answer 1

2

You need to change the Actions from "Trace" to "Break" When the condition is true the action will execute.

enter image description here

4
  • Still the same issue changing breakpoint from trace to break.
    – Moonslate
    Jan 9, 2020 at 17:29
  • Do you have another idea?
    – Moonslate
    Jan 20, 2020 at 3:00
  • are you using gdbserver, qemu, openOCD or something else as the "Gdb stub" ? I would check with gdb command you can set the conditional breakpoint i.e. break <location> if $r2 == 40. Jan 20, 2020 at 8:06
  • In the output window, I select GDB and type break <location> if $r2 == 40 (changing <location> to the adress) and hit enter. The error is: <error sending command to monitor>. I'm using mGBA to debug a GBA Advance game
    – Moonslate
    Jan 20, 2020 at 15:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.