You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Not implemented stop reason (assuming exception): watchpoint-trigger #277
Using GDB 10.1, stepping and printing values works in general.
When I add a watch like the following *(char(*)[8])(0x7fd9166daa8a) I can directly see its current value and also see the value when GDB halts. But it seems to be more of a monitor as it does not stop when the variable changes. This may also be the reason
When I use the debugging console to manually add it watch *(char(*)[8])(0x7fd9166daa8a) then the program does stop as expected and also shows the old and new variant (as expected); but there is a notification and error message, which is bad.
Please catch the event and gracefully stop + update the value in the watch pane (or add it to the watch if it isn't included already).
Activity
GitMensch commentedon Jul 19, 2021
Obviously there are more watchpoint related triggers:
That should be added to the current list in the backend:
code-debug/src/backend/mi2/mi2.ts
Lines 346 to 365 in c024e2c
prevent errors on stop, initial watchpoint handling