This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/17764] Excessive seeking when reading debug data pegs the CPU @100%
- From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 27 Dec 2014 15:52:56 +0000
- Subject: [Bug gdb/17764] Excessive seeking when reading debug data pegs the CPU @100%
- Auto-submitted: auto-generated
- References: <bug-17764-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17764
Jan Kratochvil <jan.kratochvil at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jan.kratochvil at redhat dot com
--- Comment #1 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
Try to run /usr/bin/gdb-add-index on your build before benchmarking anything.
Performance issues in files without .gdb_index are in fact
unsupported/unsupportable. How to make it automatic is another question, gold
can do that on each link but Fedora is still using GNU ld.
If it is slow even with .gdb_index (from gdb-add-index) then I need rather perf
or gprof output. Those lseek()s are mostly harmless, that is a bug in glibc
that each fseek() needlessly propagates as lseek().
--
You are receiving this mail because:
You are on the CC list for the bug.