aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc/gdb.texinfo
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2013-06-27 19:17:27 +0000
committerPedro Alves <palves@redhat.com>2013-06-27 19:17:27 +0000
commite5823f1cb51a024d11a2953dc3a07af99439b261 (patch)
tree0e1d4135acf5818db14f523b323aea2f4815dd38 /gdb/doc/gdb.texinfo
parenta8c97a8765cba36112e27b21e62672471d277876 (diff)
downloadgdb-e5823f1cb51a024d11a2953dc3a07af99439b261.zip
gdb-e5823f1cb51a024d11a2953dc3a07af99439b261.tar.gz
gdb-e5823f1cb51a024d11a2953dc3a07af99439b261.tar.bz2
Move comment on the 'stepping over resolver' mechanism to the internals manual.
This whole comment is now a bit out of place. I looked into moving it to handle_inferior_event, close to where in_solib_dynsym_resolve_code is used, but then there are 3 such places. I then looked at fragmenting it, pushing bits closer to the definitions of in_solib_dynsym_resolve_code and gdbarch_skip_solib_resolver, but then we'd lose the main advantage which is the overview. In the end, I realized this can fit nicely as internals manual material. This could possibly be a subsection of a new "run control", or "source stepping" or "stepping" or some such a bit more general section, but we can do that when we have more related content... Even the "single stepping" section is presently empty... gdb/doc/ 2013-06-27 Pedro Alves <palves@redhat.com> * gdbint.texinfo (Algorithms) <Stepping over runtime loader dynamic symbol resolution code>: New section, based on infrun.c comment. gdb/ 2013-06-27 Pedro Alves <palves@redhat.com> * infrun.c: Remove comment describing the 'stepping over runtime loader dynamic symbol resolution code' mechanism; moved to gdbint.texinfo.
Diffstat (limited to 'gdb/doc/gdb.texinfo')
0 files changed, 0 insertions, 0 deletions