This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[RFA/doco] document gdb.init check only performed in home directory


One of my coworkers working on Windows pointed out that GDB wasn't
warning him if a gdb.ini file existed in the current directory.
The documentation is a little ambiguous and might be suggesting that
GDB checks all locations where a gdbinit might be located for gdb.ini

As far as I can tell, the use of gdb.ini for Windows was discontinued
around the end of 2001. I really don't see the point of adding even
more code to try to warn users about a file that we haven't used in
over 10 years. For now, I suggest the attached patch, which just
clarifies the current situation regarding this warning.


        * gdb.texinfo (Startup): Clarify scope of gdb.ini warning for
        Windows ports.

Tested on x86_64-linux. OK to apply?


 gdb/doc/gdb.texinfo |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index c2c7745..19c329b 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -1367,8 +1367,8 @@ The @value{GDBN} init files are normally called @file{.gdbinit}.
 The DJGPP port of @value{GDBN} uses the name @file{gdb.ini}, due to
 the limitations of file names imposed by DOS filesystems.  The Windows
 ports of @value{GDBN} use the standard name, but if they find a
-@file{gdb.ini} file, they warn you about that and suggest to rename
-the file to the standard name.
+@file{gdb.ini} file in your home directory, they warn you about that
+and suggest to rename the file to the standard name.
 @node Quitting GDB

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]