Hi,
It looks like the command responsible for the delay is “-stack-list-frames”. This may happen if the algorithm used to discover stack frames does not detect the outermost frame properly and keeps on trying to interpret garbage after the end of stack.
This could be caused by the layout of your program or a bug in gdb, but you can fairly easily limit it by running the following command:
set backtrace limit <number>
where <number> is the maximum number of frames you are interested in. You can start with something like ‘3’ and see if it increases the performance. If this helps, you can add the command to the Additional GDB Commands page in VisualGDB Project Properties.