Emacs is linked. With LD_RUN_PATH set, the linker will include a
specified run-time search path in the executable.
-On some systems, Emacs could crash due to problems with dynamic
+On some systems, Emacs can crash due to problems with dynamic
linking. Specifically, on SGI Irix 6.5, crashes were reported with
backtraces like this:
4 _rld_text_resolve(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
["/comp2/mtibuild/v73/workarea/v7.3/rld/rld_bridge.s":175, 0xfb6032c]
-(`rld' is the dynamic linker.) We don't know yet why does this
-happen, but setting the environment variable LD_BIND_NOW to 1 (which
+(`rld' is the dynamic linker.) We don't know yet why this
+happens, but setting the environment variable LD_BIND_NOW to 1 (which
forces the dynamic linker to bind all shared objects early on) seems
to work around the problem.
for its ordinary input and output. This is called the GUD buffer. The
debugger displays the source files of the program by visiting them in
Emacs buffers. An arrow (@samp{=>}) in one of these buffers indicates
-the current execution line.@footnote{Under a window system the arrow is
-displayed in the marginal area of the Emacs window, called @dfn{the
-fringe}.} Moving point in this buffer does not move the arrow.
+the current execution line.@footnote{Under a window system, the arrow
+appears in the left fringe of the Emacs window.} Moving point in this
+buffer does not move the arrow.
You can start editing these source files at any time in the buffers
that display them. The arrow is not part of the file's