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
This only happens with icount enabled. I have seen this on x86 32-bit, and on x86_64 with CONFIG_MP_NUM_CPUS=1 (which enables icount since we only have one CPU)
To Reproduce
Steps to reproduce the behavior:
Build some test application and set a watch to some symbol or memory address in RAM in GDB
Continue execution
Expected behavior
GDB watches the memory as expected.
Impact
Annoyance to moderate. Disabling icount adds variance to test results and things may not be reproducible, and x86 is VERY difficult to get a real debugger attached for HW testing
The text was updated successfully, but these errors were encountered:
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.
Describe the bug
If I try to watch a memory address:
The emulator explodes:
This only happens with icount enabled. I have seen this on x86 32-bit, and on x86_64 with CONFIG_MP_NUM_CPUS=1 (which enables icount since we only have one CPU)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
GDB watches the memory as expected.
Impact
Annoyance to moderate. Disabling icount adds variance to test results and things may not be reproducible, and x86 is VERY difficult to get a real debugger attached for HW testing
The text was updated successfully, but these errors were encountered: