Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Felix Lee <felix.1@canids.net>
To: gdb@sources.redhat.com
Subject: Re: target-dependent .gdbinit
Date: Thu, 02 Jan 2003 20:04:00 -0000	[thread overview]
Message-ID: <200301022003.h02K3IB25109@paper-wolf-solo.tigerfood.org> (raw)
In-Reply-To: <3E148F45.5020502@redhat.com> on Thu, 02 Jan 2003 19:13:09 GMT.

Andrew Cagney <ac131313@redhat.com>:
> It should be kept simple.  A GDB install should only read `.gdbinit' 
> (the vx hacks, I think, should just go).  A user is then free to 
> customize their .gdbinit to do things like read .gdbinit-$target, or 
> even conditionally interpret sections of the init file.

yes, but if I'm the gdb maintainer for a site installation,
then sometimes I'll want site-wide gdbinit to handle
pecularities of the site.  telling all the users, "put this
in your .gdbinit" is unwieldy, especially if it may change
in the future.

specific instance of target-dependent .gdbinit: I've got a
gdb that will examine core files from a target OS with
shared library support.  gdb shouldn't try to map in the
host OS shared libraries.  the simple solution is to set
solib-absolute-prefix to a location that has the target OS
shared libs.  this is something you'd want to do in a
target-specific .gdbinit.  there is not necessarily one
setting that applies to the entire site.
--


  reply	other threads:[~2003-01-02 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28 10:59 Felix Lee
2003-01-02 15:08 ` Andrew Cagney
2003-01-02 18:53   ` Felix Lee
2003-01-02 19:13     ` Andrew Cagney
2003-01-02 20:04       ` Felix Lee [this message]
2003-01-02 20:17         ` Daniel Jacobowitz

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=200301022003.h02K3IB25109@paper-wolf-solo.tigerfood.org \
    --to=felix.1@canids.net \
    --cc=gdb@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