This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug symtab/17003] New: default_iterate_over_objfiles_in_search_order: broken code or broken comment?
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 30 May 2014 20:45:49 +0000
- Subject: [Bug symtab/17003] New: default_iterate_over_objfiles_in_search_order: broken code or broken comment?
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17003
Bug ID: 17003
Summary: default_iterate_over_objfiles_in_search_order: broken
code or broken comment?
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: symtab
Assignee: unassigned at sourceware dot org
Reporter: dje at google dot com
Which is right, the function comment or the implementation?
If I ignore both and go with what I think the default should be,
current_objfile should be searched first, and then we should iterate over all
objfiles (ignoring current_objfile - already searched).
objfiles.c:
/* The default implementation for the "iterate_over_objfiles_in_search_order"
gdbarch method. It is equivalent to use the ALL_OBJFILES macro,
searching the objfiles in the order they are stored internally,
ignoring CURRENT_OBJFILE.
On most platorms, it should be close enough to doing the best
we can without some knowledge specific to the architecture. */
void
default_iterate_over_objfiles_in_search_order
(struct gdbarch *gdbarch,
iterate_over_objfiles_in_search_order_cb_ftype *cb,
void *cb_data, struct objfile *current_objfile)
{
int stop = 0;
struct objfile *objfile;
ALL_OBJFILES (objfile)
{
stop = cb (objfile, cb_data);
if (stop)
return;
}
}
--
You are receiving this mail because:
You are on the CC list for the bug.