Terminally slow (75 seconds) on some steps
Andrew Cagney
ac131313@redhat.com
Tue Aug 5 05:20:00 GMT 2003
> On Mon, 21 Jul 2003 10:21:08 -0400 Andrew Cagney <ac131313@redhat.com> wrote:
>
>
>> So 11 seconds after you typed `run'.
>> (The word startup can either be appled to that time after "run", or the
>> time for gdb to reach the first "(gdb)" prompt :-().
>
>
> Sorry, 11 seconds after "run" command. Gdb startup takes about one
> second.
good (but the time is bad).
>> Lots of shared libraries?
Ok, during library load, GDB has to constantly start/stop the target -
and that slows things down. Would you be able to oprofile your entire
system so its possible to see exactly where that 11 seconds goes?
A simple gprof isn't sufficient: it is the combination of GDB <->
libthread-db? <-> kernel <-> program, that slows things down.
The speed improvement in moving from 5.2 -> 5.2 came from identifying a
situtation where GDB was performing millions of system calls. There
will likely be other cases.
I suspect, because of what you'r using, GDB is loading up libthread-db
and that may also add to the load.
Andrew
More information about the Gdb
mailing list