bug#10580: 24.0.92; gdb initialization takes more than one minute at 100% CPU

[Chong Yidong]

Dov Grobgeld <dov.grobgeld@gmail.com> writes:

> Indeed, my result is much fatter.
>
> (safe-length gdb-debug-log) => 223
>
> and the total length of the messages is about 800k. So it seems that
> the time spent is simply the parsing of this large chunk of data? What
> gdb command is run that outputs all the file="..." commands?

Those are status messages from turning on GDB's MI (machine interface)
system, I think, though I don't see why it makes so much difference in
your case.

If you type, from the shell,

  gdb -i=mi YOUR-BINARY
  r

do you similarly see a huge output?