Files
oldlinux-files/Ref-docs/manual gdb/gdbint/gdbint_8.html
2024-02-19 00:21:47 -05:00

536 lines
19 KiB
HTML

<HTML>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- Created on October, 18 2002 by texi2html 1.64 -->
<!--
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
Olaf Bachmann <obachman@mathematik.uni-kl.de>
and many others.
Maintained by: Olaf Bachmann <obachman@mathematik.uni-kl.de>
Send bugs and suggestions to <texi2html@mathematik.uni-kl.de>
-->
<HEAD>
<TITLE>GDB Internals: Host Definition</TITLE>
<META NAME="description" CONTENT="GDB Internals: Host Definition">
<META NAME="keywords" CONTENT="GDB Internals: Host Definition">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META NAME="Generator" CONTENT="texi2html 1.64">
</HEAD>
<BODY LANG="" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000">
<A NAME="SEC63"></A>
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_7.html#SEC62"> &lt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_8.html#SEC64"> &gt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_9.html#SEC67"> &lt;&lt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint.html#SEC_Top"> Up </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_9.html#SEC67"> &gt;&gt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint.html#SEC_Top">Top</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_toc.html#SEC_Contents">Contents</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_19.html#SEC186">Index</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_abt.html#SEC_About"> ? </A>]</TD>
</TR></TABLE>
<H1> 8. Host Definition </H1>
<!--docid::SEC63::-->
<P>
With the advent of Autoconf, it's rarely necessary to have host
definition machinery anymore. The following information is provided,
mainly, as an historical reference.
</P><P>
<HR SIZE="6">
<A NAME="SEC64"></A>
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_8.html#SEC63"> &lt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_8.html#SEC66"> &gt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_8.html#SEC63"> &lt;&lt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_8.html#SEC63"> Up </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_9.html#SEC67"> &gt;&gt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint.html#SEC_Top">Top</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_toc.html#SEC_Contents">Contents</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_19.html#SEC186">Index</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_abt.html#SEC_About"> ? </A>]</TD>
</TR></TABLE>
<H2> 8.1 Adding a New Host </H2>
<!--docid::SEC64::-->
<P>
<A NAME="IDX142"></A>
<A NAME="IDX143"></A>
GDB's host configuration support normally happens via Autoconf.
New host-specific definitions should not be needed. Older hosts
GDB still use the host-specific definitions and files listed
below, but these mostly exist for historical reasons, and will
eventually disappear.
</P><P>
<DL COMPACT>
<DT><TT>`gdb/config/<VAR>arch</VAR>/<VAR>xyz</VAR>.mh'</TT>
<DD>This file once contained both host and native configuration information
(see section <A HREF="gdbint_11.html#SEC95">11. Native Debugging</A>) for the machine <VAR>xyz</VAR>. The host
configuration information is now handed by Autoconf.
<P>
Host configuration information included a definition of
<CODE>XM_FILE=xm-<VAR>xyz</VAR>.h</CODE> and possibly definitions for <CODE>CC</CODE>,
<CODE>SYSV_DEFINE</CODE>, <CODE>XM_CFLAGS</CODE>, <CODE>XM_ADD_FILES</CODE>,
<CODE>XM_CLIBS</CODE>, <CODE>XM_CDEPS</CODE>, etc.; see <TT>`Makefile.in'</TT>.
</P><P>
New host only configurations do not need this file.
</P><P>
<DT><TT>`gdb/config/<VAR>arch</VAR>/xm-<VAR>xyz</VAR>.h'</TT>
<DD>This file once contained definitions and includes required when hosting
gdb on machine <VAR>xyz</VAR>. Those definitions and includes are now
handled by Autoconf.
<P>
New host and native configurations do not need this file.
</P><P>
<EM>Maintainer's note: Some hosts continue to use the <TT>`xm-xyz.h'</TT>
file to define the macros <VAR>HOST_FLOAT_FORMAT</VAR>,
<VAR>HOST_DOUBLE_FORMAT</VAR> and <VAR>HOST_LONG_DOUBLE_FORMAT</VAR>. That code
also needs to be replaced with either an Autoconf or run-time test.</EM>
</P><P>
</DL>
<P>
<A NAME="SEC65"></A>
<H3> Generic Host Support Files </H3>
<!--docid::SEC65::-->
<P>
<A NAME="IDX144"></A>
There are some "generic" versions of routines that can be used by
various systems. These can be customized in various ways by macros
defined in your <TT>`xm-<VAR>xyz</VAR>.h'</TT> file. If these routines work for
the <VAR>xyz</VAR> host, you can just include the generic file's name (with
<SAMP>`.o'</SAMP>, not <SAMP>`.c'</SAMP>) in <CODE>XDEPFILES</CODE>.
</P><P>
Otherwise, if your machine needs custom support routines, you will need
to write routines that perform the same functions as the generic file.
Put them into <CODE><VAR>xyz</VAR>-xdep.c</CODE>, and put <CODE><VAR>xyz</VAR>-xdep.o</CODE>
into <CODE>XDEPFILES</CODE>.
</P><P>
<DL COMPACT>
<A NAME="IDX145"></A>
<A NAME="IDX146"></A>
<DT><TT>`ser-unix.c'</TT>
<DD>This contains serial line support for Unix systems. This is always
included, via the makefile variable <CODE>SER_HARDWIRE</CODE>; override this
variable in the <TT>`.mh'</TT> file to avoid it.
<P>
<DT><TT>`ser-go32.c'</TT>
<DD>This contains serial line support for 32-bit programs running under DOS,
using the DJGPP (a.k.a. GO32) execution environment.
<P>
<A NAME="IDX147"></A>
<DT><TT>`ser-tcp.c'</TT>
<DD>This contains generic TCP support using sockets.
</DL>
<P>
<HR SIZE="6">
<A NAME="SEC66"></A>
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_8.html#SEC64"> &lt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_9.html#SEC67"> &gt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_8.html#SEC63"> &lt;&lt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_8.html#SEC63"> Up </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_9.html#SEC67"> &gt;&gt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint.html#SEC_Top">Top</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_toc.html#SEC_Contents">Contents</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_19.html#SEC186">Index</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_abt.html#SEC_About"> ? </A>]</TD>
</TR></TABLE>
<H2> 8.2 Host Conditionals </H2>
<!--docid::SEC66::-->
<P>
When GDB is configured and compiled, various macros are
defined or left undefined, to control compilation based on the
attributes of the host system. These macros and their meanings (or if
the meaning is not documented here, then one of the source files where
they are used is indicated) are:
</P><P>
<DL COMPACT>
<A NAME="IDX148"></A>
<DT><CODE>GDBINIT_FILENAME</CODE>
<DD><A NAME="IDX149"></A>
The default name of GDB's initialization file (normally
<TT>`.gdbinit'</TT>).
<P>
<A NAME="IDX150"></A>
<DT><CODE>NO_STD_REGS</CODE>
<DD><A NAME="IDX151"></A>
This macro is deprecated.
<P>
<A NAME="IDX152"></A>
<DT><CODE>NO_SYS_FILE</CODE>
<DD><A NAME="IDX153"></A>
Define this if your system does not have a <CODE>&#60;sys/file.h&#62;</CODE>.
<P>
<A NAME="IDX154"></A>
<DT><CODE>SIGWINCH_HANDLER</CODE>
<DD><A NAME="IDX155"></A>
If your host defines <CODE>SIGWINCH</CODE>, you can define this to be the name
of a function to be called if <CODE>SIGWINCH</CODE> is received.
<P>
<A NAME="IDX156"></A>
<DT><CODE>SIGWINCH_HANDLER_BODY</CODE>
<DD><A NAME="IDX157"></A>
Define this to expand into code that will define the function named by
the expansion of <CODE>SIGWINCH_HANDLER</CODE>.
<P>
<A NAME="IDX158"></A>
<DT><CODE>ALIGN_STACK_ON_STARTUP</CODE>
<DD><A NAME="IDX159"></A>
<A NAME="IDX160"></A>
Define this if your system is of a sort that will crash in
<CODE>tgetent</CODE> if the stack happens not to be longword-aligned when
<CODE>main</CODE> is called. This is a rare situation, but is known to occur
on several different types of systems.
<P>
<A NAME="IDX161"></A>
<DT><CODE>CRLF_SOURCE_FILES</CODE>
<DD><A NAME="IDX162"></A>
<A NAME="IDX163"></A>
Define this if host files use <CODE>\r\n</CODE> rather than <CODE>\n</CODE> as a
line terminator. This will cause source file listings to omit <CODE>\r</CODE>
characters when printing and it will allow <CODE>\r\n</CODE> line endings of files
which are "sourced" by gdb. It must be possible to open files in binary
mode using <CODE>O_BINARY</CODE> or, for fopen, <CODE>"rb"</CODE>.
<P>
<A NAME="IDX164"></A>
<DT><CODE>DEFAULT_PROMPT</CODE>
<DD><A NAME="IDX165"></A>
<A NAME="IDX166"></A>
The default value of the prompt string (normally <CODE>"(gdb) "</CODE>).
<P>
<A NAME="IDX167"></A>
<DT><CODE>DEV_TTY</CODE>
<DD><A NAME="IDX168"></A>
<A NAME="IDX169"></A>
The name of the generic TTY device, defaults to <CODE>"/dev/tty"</CODE>.
<P>
<A NAME="IDX170"></A>
<DT><CODE>FCLOSE_PROVIDED</CODE>
<DD><A NAME="IDX171"></A>
Define this if the system declares <CODE>fclose</CODE> in the headers included
in <CODE>defs.h</CODE>. This isn't needed unless your compiler is unusually
anal.
<P>
<A NAME="IDX172"></A>
<DT><CODE>FOPEN_RB</CODE>
<DD><A NAME="IDX173"></A>
Define this if binary files are opened the same way as text files.
<P>
<A NAME="IDX174"></A>
<DT><CODE>GETENV_PROVIDED</CODE>
<DD><A NAME="IDX175"></A>
Define this if the system declares <CODE>getenv</CODE> in its headers included
in <CODE>defs.h</CODE>. This isn't needed unless your compiler is unusually
anal.
<P>
<A NAME="IDX176"></A>
<DT><CODE>HAVE_MMAP</CODE>
<DD><A NAME="IDX177"></A>
<A NAME="IDX178"></A>
In some cases, use the system call <CODE>mmap</CODE> for reading symbol
tables. For some machines this allows for sharing and quick updates.
<P>
<A NAME="IDX179"></A>
<DT><CODE>HAVE_TERMIO</CODE>
<DD><A NAME="IDX180"></A>
Define this if the host system has <CODE>termio.h</CODE>.
<P>
<A NAME="IDX181"></A>
<DT><CODE>INT_MAX</CODE>
<DD><A NAME="IDX182"></A>
<A NAME="IDX183"></A>
<DT><CODE>INT_MIN</CODE>
<DD><A NAME="IDX184"></A>
<A NAME="IDX185"></A>
<DT><CODE>LONG_MAX</CODE>
<DD><A NAME="IDX186"></A>
<A NAME="IDX187"></A>
<DT><CODE>UINT_MAX</CODE>
<DD><A NAME="IDX188"></A>
<A NAME="IDX189"></A>
<DT><CODE>ULONG_MAX</CODE>
<DD><A NAME="IDX190"></A>
Values for host-side constants.
<P>
<A NAME="IDX191"></A>
<DT><CODE>ISATTY</CODE>
<DD><A NAME="IDX192"></A>
Substitute for isatty, if not available.
<P>
<A NAME="IDX193"></A>
<DT><CODE>LONGEST</CODE>
<DD><A NAME="IDX194"></A>
This is the longest integer type available on the host. If not defined,
it will default to <CODE>long long</CODE> or <CODE>long</CODE>, depending on
<CODE>CC_HAS_LONG_LONG</CODE>.
<P>
<A NAME="IDX195"></A>
<DT><CODE>CC_HAS_LONG_LONG</CODE>
<DD><A NAME="IDX196"></A>
<A NAME="IDX197"></A>
Define this if the host C compiler supports <CODE>long long</CODE>. This is set
by the <CODE>configure</CODE> script.
<P>
<A NAME="IDX198"></A>
<DT><CODE>PRINTF_HAS_LONG_LONG</CODE>
<DD><A NAME="IDX199"></A>
Define this if the host can handle printing of long long integers via
the printf format conversion specifier <CODE>ll</CODE>. This is set by the
<CODE>configure</CODE> script.
<P>
<A NAME="IDX200"></A>
<DT><CODE>HAVE_LONG_DOUBLE</CODE>
<DD><A NAME="IDX201"></A>
Define this if the host C compiler supports <CODE>long double</CODE>. This is
set by the <CODE>configure</CODE> script.
<P>
<A NAME="IDX202"></A>
<DT><CODE>PRINTF_HAS_LONG_DOUBLE</CODE>
<DD><A NAME="IDX203"></A>
Define this if the host can handle printing of long double float-point
numbers via the printf format conversion specifier <CODE>Lg</CODE>. This is
set by the <CODE>configure</CODE> script.
<P>
<A NAME="IDX204"></A>
<DT><CODE>SCANF_HAS_LONG_DOUBLE</CODE>
<DD><A NAME="IDX205"></A>
Define this if the host can handle the parsing of long double
float-point numbers via the scanf format conversion specifier
<CODE>Lg</CODE>. This is set by the <CODE>configure</CODE> script.
<P>
<A NAME="IDX206"></A>
<DT><CODE>LSEEK_NOT_LINEAR</CODE>
<DD><A NAME="IDX207"></A>
Define this if <CODE>lseek (n)</CODE> does not necessarily move to byte number
<CODE>n</CODE> in the file. This is only used when reading source files. It
is normally faster to define <CODE>CRLF_SOURCE_FILES</CODE> when possible.
<P>
<A NAME="IDX208"></A>
<DT><CODE>L_SET</CODE>
<DD><A NAME="IDX209"></A>
This macro is used as the argument to <CODE>lseek</CODE> (or, most commonly,
<CODE>bfd_seek</CODE>). FIXME, should be replaced by SEEK_SET instead,
which is the POSIX equivalent.
<P>
<A NAME="IDX210"></A>
<DT><CODE>MMAP_BASE_ADDRESS</CODE>
<DD><A NAME="IDX211"></A>
When using HAVE_MMAP, the first mapping should go at this address.
<P>
<A NAME="IDX212"></A>
<DT><CODE>MMAP_INCREMENT</CODE>
<DD><A NAME="IDX213"></A>
when using HAVE_MMAP, this is the increment between mappings.
<P>
<A NAME="IDX214"></A>
<DT><CODE>NORETURN</CODE>
<DD><A NAME="IDX215"></A>
If defined, this should be one or more tokens, such as <CODE>volatile</CODE>,
that can be used in both the declaration and definition of functions to
indicate that they never return. The default is already set correctly
if compiling with GCC. This will almost never need to be defined.
<P>
<A NAME="IDX216"></A>
<DT><CODE>ATTR_NORETURN</CODE>
<DD><A NAME="IDX217"></A>
If defined, this should be one or more tokens, such as
<CODE>__attribute__ ((noreturn))</CODE>, that can be used in the declarations
of functions to indicate that they never return. The default is already
set correctly if compiling with GCC. This will almost never need to be
defined.
<P>
<A NAME="IDX218"></A>
<DT><CODE>USE_GENERIC_DUMMY_FRAMES</CODE>
<DD><A NAME="IDX219"></A>
<A NAME="IDX220"></A>
Define this to 1 if the target is using the generic inferior function
call code. See <CODE>blockframe.c</CODE> for more information.
<P>
<A NAME="IDX221"></A>
<DT><CODE>USE_MMALLOC</CODE>
<DD><A NAME="IDX222"></A>
<A NAME="IDX223"></A>
GDB will use the <CODE>mmalloc</CODE> library for memory allocation
for symbol reading if this symbol is defined. Be careful defining it
since there are systems on which <CODE>mmalloc</CODE> does not work for some
reason. One example is the DECstation, where its RPC library can't
cope with our redefinition of <CODE>malloc</CODE> to call <CODE>mmalloc</CODE>.
When defining <CODE>USE_MMALLOC</CODE>, you will also have to set
<CODE>MMALLOC</CODE> in the Makefile, to point to the <CODE>mmalloc</CODE> library. This
define is set when you configure with <SAMP>`--with-mmalloc'</SAMP>.
<P>
<A NAME="IDX224"></A>
<DT><CODE>NO_MMCHECK</CODE>
<DD><A NAME="IDX225"></A>
<A NAME="IDX226"></A>
Define this if you are using <CODE>mmalloc</CODE>, but don't want the overhead
of checking the heap with <CODE>mmcheck</CODE>. Note that on some systems,
the C runtime makes calls to <CODE>malloc</CODE> prior to calling <CODE>main</CODE>, and if
<CODE>free</CODE> is ever called with these pointers after calling
<CODE>mmcheck</CODE> to enable checking, a memory corruption abort is certain
to occur. These systems can still use <CODE>mmalloc</CODE>, but must define
<CODE>NO_MMCHECK</CODE>.
<P>
<A NAME="IDX227"></A>
<DT><CODE>MMCHECK_FORCE</CODE>
<DD><A NAME="IDX228"></A>
Define this to 1 if the C runtime allocates memory prior to
<CODE>mmcheck</CODE> being called, but that memory is never freed so we don't
have to worry about it triggering a memory corruption abort. The
default is 0, which means that <CODE>mmcheck</CODE> will only install the heap
checking functions if there has not yet been any memory allocation
calls, and if it fails to install the functions, GDB will issue a
warning. This is currently defined if you configure using
<SAMP>`--with-mmalloc'</SAMP>.
<P>
<A NAME="IDX229"></A>
<DT><CODE>NO_SIGINTERRUPT</CODE>
<DD><A NAME="IDX230"></A>
<A NAME="IDX231"></A>
Define this to indicate that <CODE>siginterrupt</CODE> is not available.
<P>
<A NAME="IDX232"></A>
<DT><CODE>SEEK_CUR</CODE>
<DD><A NAME="IDX233"></A>
<A NAME="IDX234"></A>
<DT><CODE>SEEK_SET</CODE>
<DD><A NAME="IDX235"></A>
Define these to appropriate value for the system <CODE>lseek</CODE>, if not already
defined.
<P>
<A NAME="IDX236"></A>
<DT><CODE>STOP_SIGNAL</CODE>
<DD><A NAME="IDX237"></A>
This is the signal for stopping GDB. Defaults to
<CODE>SIGTSTP</CODE>. (Only redefined for the Convex.)
<P>
<A NAME="IDX238"></A>
<DT><CODE>USE_O_NOCTTY</CODE>
<DD><A NAME="IDX239"></A>
Define this if the interior's tty should be opened with the <CODE>O_NOCTTY</CODE>
flag. (FIXME: This should be a native-only flag, but <TT>`inflow.c'</TT> is
always linked in.)
<P>
<A NAME="IDX240"></A>
<DT><CODE>USG</CODE>
<DD><A NAME="IDX241"></A>
Means that System V (prior to SVR4) include files are in use. (FIXME:
This symbol is abused in <TT>`infrun.c'</TT>, <TT>`regex.c'</TT>,
<TT>`remote-nindy.c'</TT>, and <TT>`utils.c'</TT> for other things, at the
moment.)
<P>
<A NAME="IDX242"></A>
<DT><CODE>lint</CODE>
<DD><A NAME="IDX243"></A>
Define this to help placate <CODE>lint</CODE> in some situations.
<P>
<A NAME="IDX244"></A>
<DT><CODE>volatile</CODE>
<DD><A NAME="IDX245"></A>
Define this to override the defaults of <CODE>__volatile__</CODE> or
<CODE>/**/</CODE>.
</DL>
<P>
<A NAME="Target Architecture Definition"></A>
</P><P>
<HR SIZE="6">
<TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
<TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_8.html#SEC63"> &lt;&lt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_9.html#SEC67"> &gt;&gt; </A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint.html#SEC_Top">Top</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_toc.html#SEC_Contents">Contents</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_19.html#SEC186">Index</A>]</TD>
<TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="gdbint_abt.html#SEC_About"> ? </A>]</TD>
</TR></TABLE>
<BR>
<FONT SIZE="-1">
<address>
<p>Please send FSF &amp; GNU inquiries &amp; questions to <a
href="mailto:gnu@gnu.org">gnu@gnu.org</a>. There are also <a
href="http://www.gnu.org/home.html#ContactInfo">other ways to
contact</a> the FSF.</p>
<p>These pages are maintained by <a
href="http://www.gnu.org/software/gdb/">the GDB developers</a>.</p>
<p>Copyright Free Software Foundation, Inc., 59 Temple Place - Suite
330, Boston, MA 02111, USA.</p>
<p>Verbatim copying and distribution of this entire article is
permitted in any medium, provided this notice is preserved.</p>
</address>
This document was generated
by <I>GDB Administrator</I> on <I>October, 18 2002</I>
using <A HREF="http://www.mathematik.uni-kl.de/~obachman/Texi2html
"><I>texi2html</I></A>
</BODY>
</HTML>