From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Smith John <horserivers@gmail.com>, gdb@sourceware.org
Subject: Re: .gdbini file
Date: Wed, 15 Aug 2012 17:35:00 -0000 [thread overview]
Message-ID: <CADPb22Qqg5kWi4M6sYx7C7_7=+mSxoTQOfVyotdwGbvtUyLsnw@mail.gmail.com> (raw)
In-Reply-To: <83vcgpddpa.fsf@gnu.org>
On Sat, Aug 11, 2012 at 1:40 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sat, 11 Aug 2012 15:30:23 +0800
>> From: Smith John <horserivers@gmail.com>
>>
>> I am debugging gdb with itself , how can I use the
>> gdbinit file in the gdb source directory?
>
> Either type the "source /path/to/.gdbinit" command at the GDB prompt,
> or start GDB from the directory of that file, so that it is loaded
> automatically.
>
>> or what role does this file play on ?
>
> It defines several defaults and commands useful for debugging GDB.
> It's a text file, so you can read it and see what it does.
Remember that .gdbinit is gone, in favor of gdb-gdb.gdb [there's a
reason it's spelled that way :-)]
And there should be no need to manually load it, that should happen
automatically (except when debugging a newer gdb with an older gdb).
For reference sake,
- gdb-gdb.gdb is installed in the build tree from gdb-gdb.gdb.in in
the source tree
- there is also gdb-gdb.py, which provides additional Python based
support for debugging gdb with gdb.
next prev parent reply other threads:[~2012-08-15 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 7:30 Smith John
2012-08-11 8:40 ` Eli Zaretskii
2012-08-15 17:35 ` Doug Evans [this message]
2012-08-15 18:09 ` Terekhov, Mikhail
2012-08-15 19:32 ` dje
2012-08-15 18:22 ` Tom Tromey
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='CADPb22Qqg5kWi4M6sYx7C7_7=+mSxoTQOfVyotdwGbvtUyLsnw@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=horserivers@gmail.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