This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug compile/17938] New: Calling clear_symtab_users is indeed too costly
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 06 Feb 2015 19:14:28 +0000
- Subject: [Bug compile/17938] New: Calling clear_symtab_users is indeed too costly
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17938
Bug ID: 17938
Summary: Calling clear_symtab_users is indeed too costly
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: compile
Assignee: unassigned at sourceware dot org
Reporter: dje at google dot com
compile-object-run.c has this:
/* It may be a bit too pervasive in this dummy_frame dtor callback. */
clear_symtab_users (0);
This is indeed too pervasive (costly).
Python scripts will get a clear_objfiles event which an trigger large scale
flushing of cached data. Plus it will flush the symbol lookup cache.
Earlier the function does this:
free_objfile (objfile);
What we need on the python side is an objfile_freed event.
Are there other reasons why clear_symtab_users is called here?
I see that free_objfile does some of the things that clear_symtab_users does.
--
You are receiving this mail because:
You are on the CC list for the bug.