This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: typo in gdb.texinfo
- To: Dmitry Sivachenko <dima at Chg dot RU>
- Subject: Re: typo in gdb.texinfo
- From: Michael Snyder <msnyder at cygnus dot com>
- Date: Wed, 15 Mar 2000 11:36:42 -0800
- CC: gdb-patches at sourceware dot cygnus dot com
- Organization: Cygnus Solutions
- References: <200003151932.WAA39200@netserv1.chg.ru>
Dmitry Sivachenko wrote:
>
> There is no value for GDBINIT!
> Consider this fix:
>
> --dima
>
> --- gdb.texinfo.orig Wed Mar 15 22:31:16 2000
> +++ gdb.texinfo Wed Mar 15 22:31:32 2000
> @@ -10611,7 +10611,7 @@
> @cindex floating point, MIPS remote
> If your target board does not support the MIPS floating point
> coprocessor, you should use the command @samp{set mipsfpu none} (if you
> -need this, you may wish to put the command in your @value{GDBINIT}
> +need this, you may wish to put the command in your @file{.gdbinit}
> file). This tells @value{GDBN} how to find the return value of
> functions which return floating point values. It also allows
> @value{GDBN} to avoid saving the floating point registers when calling
I think the purpose of having GDBINIT be a variable is
because it has a different filename on windows/CYGWIN.
Isn't it called "gdb.ini" or something?
If the variable truly isn't defined, it probably should be.