public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: dje@google.com
To: "Terekhov, Mikhail" <mikhail.terekhov@emc.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: .gdbini file
Date: Wed, 15 Aug 2012 19:32:00 -0000	[thread overview]
Message-ID: <20523.63796.99531.936395@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <393A4D071DD24B45A370BEBB86AD05A2215CE984FF@MX37A.corp.emc.com>

Terekhov, Mikhail writes:
 > > -----Original Message-----
 > > From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
 > > Behalf Of Doug Evans
 > > Sent: Wednesday, August 15, 2012 1:35 PM
 > ...
 > > 
 > > Remember that .gdbinit is gone, in favor of gdb-gdb.gdb [there's a
 > > reason it's spelled that way :-)]
 > 
 > And the reason is?

gdb-gdb.gdb
 ^   ^   ^
 ^   ^   ^---- It's a gdb script.
 ^   ^         If it were Python this would be .py.
 ^   ^
 ^   ^-------- "-gdb" is a gdb convention, it's the suffix added to a file
 ^             for auxiliary support.
 ^             E.g., gdb will auto-load libstdc++.so-gdb.py (version elided)
 ^             which contains the std c++ pretty-printers.
 ^
 ^------------ This init script is for the program named "gdb".
               If this were for readelf the script would be named
               readelf-gdb.gdb.

Kind of a funny name, but there is a convention behind it. :-)

  reply	other threads:[~2012-08-15 19:32 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
2012-08-15 18:09     ` Terekhov, Mikhail
2012-08-15 19:32       ` dje [this message]
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=20523.63796.99531.936395@ruffy2.mtv.corp.google.com \
    --to=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=mikhail.terekhov@emc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).