From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Christopher Faylor <cgf@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: GDBINIT_FILENAME macro in config/i386/xm-cygwin.h
Date: Thu, 14 Feb 2002 08:52:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20020214173500.01d4ef38@ics.u-strasbg.fr> (raw)
In-Reply-To: <20020214163330.GA550@redhat.com>
At 17:33 14/02/2002 , Christopher Faylor a écrit:
>On Thu, Feb 14, 2002 at 05:10:42PM +0100, Pierre Muller wrote:
> >
> >
> >xm-cygwin.h seems to define again GDBINIT_FILENAME to "gdb.ini",
> >thus gdb.ini is searched in home and current dir.
> >
> >But looking into logs, Chistopher removed this in version 1.5,
> >as explained in the log, while Andrew reintroduced it,
> >but without any mention in the log.
> >
> >Isn't that an error in the last commit of Andrew?
>
>I'm sure that it is. I've reverted the reversion.
>
>Thanks for catching this. I'm sure I would have been scratching my
>head about this one for a while before I figured out what was going
>on.
Its simply because I didn't understand the meaning of the warning generated by the
_iniitialize_check_for_gdb_ini file. It said that I should rename gdb.ini to .gdbinit,
but when I did that, the file was not "sourced" anymore...
Now that its fixed again, I understand the comment.
Just one notice:
this warning is only done for the $HOME/gdb.ini file,
should it be also issued if a gdb.ini exists in the current directory?
Because the GDBINIT_FILENAME is read first in $HOME dir
and after in the starting dir of the GDB executable.
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2002-02-14 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 8:11 Pierre Muller
2002-02-14 8:33 ` Christopher Faylor
2002-02-14 8:52 ` Pierre Muller [this message]
2002-02-14 8:57 ` Christopher Faylor
2002-02-14 9:58 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.2.0.58.20020214173500.01d4ef38@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=cgf@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox