Bug 550257

Description Niko D 2019-08-20 05:45:46 EDT

I'm using Eclipse CDT to debug a remote C application on an embedded target.
The program has ~45 threads and the debugging performance is very poor.

It seems that on every step, the following actions are performed:
 1) Get thread-info for active thread (e.g. 2)
 2) Get thread-info individually for every (!) thread except the active thread (e.g. 1, 3, 4, ..., 43)
 3) Get the stack frames (stack-list-frames) for the active thread

The whole thing takes ~5s and a Wireshark capture shows that ~4000 (!) packets totalling 400kB are transferred in 4-5s.
Is it really necessary to issue the thread-info command individually for each thread?

In Wireshark I can see that for every thread, the full thread list is transferred (qXfer:threads:read) and the current stack trace (presumably) is read as well (read registers, read memory, ...).

Environment: Eclipse 4.12 running on a linux host with gdb 8.2.1. The debugged program is run on an ARM device with gdbserver 8.2.1.

The same problem also occurs with an older version of Eclipse (4.5.2 & CDT 8.8.1).