This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
(one of the parts of this profiling which is especially useful is that we have a "mi-timings-enabled" setting. When it's enabled, every MI command reports how long gdb took to complete it, e.g. the "time=" bit at the end here:
-> 50-stack-list-frames 0 5
<- 50^done,stack=[frame=
{level="0",addr="0x0009e7fc",fp="0xbfffe700",func=" [...] ,frame=
{level="5",addr="0x936265d0",fp="0xbfffeee0",func="-[NSApplication
run]"}],time=
{wallclock="0.14353",user="0.00584",system="0.00335",start="111895234 8.0
03847",end="1118952348.147372"}
Yes but what happens when the stack is much deeper, 20 or 30 say, like it can
be when you you are debugging Emacs, or GDB for that matter?
-thread-list-ids -stack-list-frames-lite -limit 500 -stack-select-frame 0 -stack-list-frames 0 0 -var-update "var1" "var2" "var3" -exec-next
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |