From: Daniel Jacobowitz <drow@false.org>
To: Jerome Guitton <guitton@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: Add support for --with-system-gdbinit
Date: Mon, 19 Jan 2009 14:20:00 -0000 [thread overview]
Message-ID: <20090119141953.GA32231@caradoc.them.org> (raw)
In-Reply-To: <20090119141053.GE45099@adacore.com>
On Mon, Jan 19, 2009 at 03:10:53PM +0100, Jerome Guitton wrote:
> Maybe we can take this opportunity to print the list of gdbinit loaded in
> GDB at startup. Something like:
>
> [...]
> --xdb XDB compatibility mode.
>
> At startup, GDB reads the following init files and executes their commands:
> * system-wide init file: /etc/gdb/gdbinit
> * user-specific init file: /homes/guitton/.gdbinit
> * local init file: /homes/guitton/work/.gdbinit
>
> For more information, type "help" from within GDB, or consult the
> GDB manual (available as on-line info or a printed manual).
> [...]
>
>
> Would that make sense?
It does to me - although I suggest using a relative path for that last
item (./.gdbinit), to make it clear that it will change if you cd.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-01-19 14:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 13:56 Daniel Jacobowitz
2009-01-14 19:39 ` Eli Zaretskii
2009-01-14 19:50 ` Daniel Jacobowitz
2009-01-14 20:22 ` Eli Zaretskii
2009-01-14 20:38 ` Daniel Jacobowitz
2009-01-14 21:55 ` Eli Zaretskii
2009-01-14 23:07 ` Daniel Jacobowitz
2009-01-15 4:10 ` Eli Zaretskii
2009-01-19 14:11 ` Jerome Guitton
2009-01-19 14:20 ` Daniel Jacobowitz [this message]
2009-01-19 18:40 ` Eli Zaretskii
2009-01-21 10:54 ` Jerome Guitton
2009-01-21 19:03 ` Eli Zaretskii
2009-01-23 17:24 ` Jerome Guitton
2009-01-23 22:55 ` Eli Zaretskii
2009-01-28 18:00 ` Jerome Guitton
2009-01-23 17:42 ` Daniel Jacobowitz
2009-01-26 9:12 ` Jerome Guitton
2009-01-26 14:59 ` Daniel Jacobowitz
2009-01-28 15:06 ` Jerome Guitton
2009-01-16 11:54 ` Jerome Guitton
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=20090119141953.GA32231@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.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