Community
Participate
Working Groups
In our non-GDB debugger we have the option of writing some complicated scripts that setup a particular bit of hardware or simulation in a specific state. This may require doing many scripted gdb-like commands (inserting breakpoints, stepping, continuing, etc). When this script generates lots of messages it causes all sorts of strange behaviour, sometimes leading to OOM errors. Even when it works fine, it can take a long time for the IDE to "catch up" with the events from GDB.
Umair Sair in Bug 530377 Comment 3 has a similar case. Bug 530377 was intended to address the related problem of fast events causing breakpoint state corruption. This bug is to address DSF becoming overwhelmed.
I will revisit this bug in the coming week to make an appropriate update to target milestone.
This bug was assigned and targeted at a now released milestone. As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and marked the bug as resolved.