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: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 27 Dec 2014 16:21:44 +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
dje at google dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dje at google dot com
--- Comment #2 from dje at google dot com ---
Yeah. All those seeks are annoying, but are they really the main cause of the
slow down?
Also, I wouldn't say the non-.gdb_index case is not supportable.
It *is* going to be slower, but if there are fixable perf issues we may fix
them
(emphasis on "may").
If the cpu is pegged at 100% and in this case debug info reading is cpu bound
and not disk bound, how big is the shared library?
If it is relatively big, .gdb_index is definitely the way to go if you want a
speedup.
--
You are receiving this mail because:
You are on the CC list for the bug.