[Bug gdb/12130] gdb: backtrace on stripped binary much slower thanon binary with debug info

["tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=12130

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |tromey at redhat dot com

--- Comment #3 from Tom Tromey <tromey at redhat dot com> 2012-07-13 18:02:08 UTC ---
With current CVS trunk gdb I get pretty similar results for both:

barimba. sh -x RunIt.sh
+ gcc -g -o pr pr.c
+ echo 'With debuginfo:'
With debuginfo:
+ gdb --batch-silent -ex run -ex 'bt -16' ./pr

real    0m21.787s
user    0m18.759s
sys    0m2.440s
+ echo 'Without debug info (stripped):'
Without debug info (stripped):
+ strip pr
+ gdb --batch-silent -ex run -ex 'bt -16' ./pr

real    0m19.851s
user    0m17.299s
sys    0m2.340s


The results are somewhat noisy, they vary between 10 and 20 seconds
on this machine.

> Would it possible to skip the symbol lookups for frames that are not shown?

Based on my reading of stack.c:backtrace_command_1, this is already done.
The "if (count < 0)" block peels off the top frames, afaik not doing
any lookups.

Could you possibly try a newer gdb and see if the problem has been fixed
for you as well?

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.