summaryrefslogtreecommitdiff
path: root/bfd/bfdio.c
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@gnat.com>2010-04-20 22:35:57 +0000
committerJoel Brobecker <brobecker@gnat.com>2010-04-20 22:35:57 +0000
commit95194f81a233801fcb414f861da13a39c0cc3825 (patch)
tree9f510135733c5a3e114bd92036fefd26803a4609 /bfd/bfdio.c
parent0a784d2742791209e8042a9c7c35f58f3cdcb36d (diff)
downloadgdb-95194f81a233801fcb414f861da13a39c0cc3825.tar.gz
procfs.c: iterate_over_mappings callback has wrong profile.
The function proc_find_memory_regions calls iterate_over_mappings as follow: > return iterate_over_mappings (pi, func, data, > find_memory_regions_callback); The problem is that both func and find_memory_regions_callback do not match the profile expected by iterate_over_mappings: > iterate_over_mappings (procinfo *pi, int (*child_func) (), void *data, > int (*func) (struct prmap *map, > int (*child_func) (), > void *data)) We cannot change proc_find_memory_regions such that FUNC is a pointer to a function that takes no argument (in place of the 6 that it has). This is because proc_find_memory_regions is used as a target_ops method. However, it turns out that changing iterate_over_mappings to conform to the profile imposed by the target_ops vector is possible without much effort. gdb/ChangeLog: * procfs.c (iterate_over_mappings_cb_ftype): New typedef. (iterate_over_mappings): Adjust function profile. Add declaration. (insert_dbx_link_bpt_in_region, info_mappings_callback): Adjust accordingly.
Diffstat (limited to 'bfd/bfdio.c')
0 files changed, 0 insertions, 0 deletions