Author Topic: debugger startup time  (Read 3610 times)

Offline u2227

  • Single posting newcomer
  • *
  • Posts: 9
debugger startup time
« on: May 05, 2008, 05:22:34 am »
I feel like debugger is very slow to start up.
I used the stop watch, and found that it takes 1.7 seconds to simply startup and reach the breakpoint.
I have Core2duo at 3.3Ghz, 2GB RAM.
My strong believe is that debugger startup time must be as small as possible for productive work!
I know C::B uses GDB as a backbone for debugging. But I made a little test, I debugged the same program with the GDB.
=======gdb.txt=====
file a.out
b 36
l
r
q
==============

time gdb --quiet --batch --command=gdb.txt

=====output======Breakpoint 1 at 0x80587e7: file main.cpp, line 36.
36         r.user = user;
37         r.info1 = info1;
38         r.info2 = info2;
39         r.info3 = info3;
40         r.get(x);
41         str f = r.get(x);
42         printf("<PRE>%s", *f);
43      }
44
45      int main(int argc, char **argv)
Content-type: text/html


Breakpoint 1, load_key (s=@0xbfbfea58, user=@0xbfbfea54, info1=@0xbfbfea50, info2=@0xbfbfea4c,
    info3=@0xbfbfea48) at main.cpp:36
36         r.user = user;
0.018u 0.006s 0:00.03 33.3%     8144+3504k 0+0io 0pf+0w

=========

as you can see the same operation: starting GDB, loading symbols, setting a breakpoint, running to breakpoint, only takes... wait, can I Read it right??!!!! it takes 0.03 seconds!! MY GOD! This IS fast!

Of course this is MY strong believe that IDE response times are it's main parameters, others might think that fancy stuff like refactoring, dialogs, charts and such are more important and have higher priority than those old-time keyboard shortcuts as "Run to cursor" "Step over". By the way step-over is also not blazing fast.