e5823f1cb5
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. |
||
|---|---|---|
| .. | ||
| a4rc.sed | ||
| agentexpr.texi | ||
| all-cfg.texi | ||
| annotate.texinfo | ||
| ChangeLog | ||
| fdl.texi | ||
| gdb.texinfo | ||
| gdbint.texinfo | ||
| gpl.texi | ||
| lpsrc.sed | ||
| LRS | ||
| Makefile.in | ||
| observer.texi | ||
| psrc.sed | ||
| refcard.tex | ||
| stabs.texinfo | ||
| stack_frame.eps | ||
| stack_frame.pdf | ||
| stack_frame.png | ||
| stack_frame.svg | ||
| stack_frame.txt | ||
