• Locked Locked
  • Replies 3 replies
  • Subscribers 122 subscribers
  • Views 4615 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Breakpoints numbering issue

claudio06

Hi

When  I remove some breakpoints in my code, and  re enable it just after  I have a non constant breakpoint index

For example:

Execution stopped in Thread mode at 0x1FFE447A
0x1FFE447A   9,0   return result;
break -p "I:/try_env/src/tests/D_IP_ISI_SYN/imx8qm/pdma_bypass_dc0_iris_fetchlayer0_di0.c":547
Breakpoint 10 at 0x1FFF9A60
    on file pdma_bypass_dc0_iris_fetchlayer0_di0.c, line 547
delete 10
Breakpoint 10 deleted
break -p "I:/try_env/src/tests/D_IP_ISI_SYN/imx8qm/pdma_bypass_dc0_iris_fetchlayer0_di0.c":547
Breakpoint 11 at 0x1FFF9A60
    on file pdma_bypass_dc0_iris_fetchlayer0_di0.c, line 547
wait
continue

It sounds last breakpoint index is not removed from internal database of DS5.

It can be annoying when doing some scripting and using bkp index.

How to overcome this issue?

Issue is poping up with latest v 5.27.0 DS5 .

regards

claude

Parents

  • Hi Claude,

    The breakpoints are being removed. It's just that the next available id is used for each new breakpoint.

    You could use the 'clear' command instead, and then still reference the symbol that you used to set the breakpoint at.

    So, for example, if you want to set a breakpoint at, say, the start of a function called 'compare_sorts()' you can do :

    break -p compare_sorts

    or if you know the offset from the function you can do :

    break -p compare_sorts+0xC

    then to delete use the 'clear' command, thus :

    clear compare_sorts

    clear compare_sorts+0xC

    Does that help you ?

    Regards,

    Stuart

Reply

  • Hi Claude,

    The breakpoints are being removed. It's just that the next available id is used for each new breakpoint.

    You could use the 'clear' command instead, and then still reference the symbol that you used to set the breakpoint at.

    So, for example, if you want to set a breakpoint at, say, the start of a function called 'compare_sorts()' you can do :

    break -p compare_sorts

    or if you know the offset from the function you can do :

    break -p compare_sorts+0xC

    then to delete use the 'clear' command, thus :

    clear compare_sorts

    clear compare_sorts+0xC

    Does that help you ?

    Regards,

    Stuart

Children