You used
GdbValueMemLimit
or
--eval-command="set print elements 10"
?
If this helps, then maybe it should be set by default to a lower value, so the problem doesnt happen at first. (Ideally, but I am not sure if that is easy to do, if the limit is hit, it should show a message...)
I will need to do some testing of my own, to see what is possible.
Also maybe set a lower value for getting the stack. Then explicit watches will still work (even if slow / or at a medium value)