Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: "Elena Zannoni" <ezannoni@redhat.com>,
	"Fernando Nasser" <fnasser@redhat.com>,
	"Felix Lee" <felix.1@canids.net>, <gdb@sources.redhat.com>
Subject: Re: patch to use target specific .gdbinit file
Date: Tue, 14 Jan 2003 19:11:00 -0000	[thread overview]
Message-ID: <000901c2bc00$aa564e80$0202040a@catdog> (raw)
In-Reply-To: <3E233DF2.6010403@redhat.com>

> > Well then a configure option isn't the answer.
>
> A configuration time option answers a problem.  Perhaps not your problem.
>

Well, it answers our problem but isn't extensible to a multi-arch situation.
It sounds like almost everyone agrees that some form of a target specific
extension to the .gdbinit mechanism would be useful but a decision about how
best to implement it hasn't been made.  What I'm going to do for now is
implement it in our port only.  We ship separate gdb binaries and are not
planning on multi-arching soon so our _initialize_nto() function is a
perfect place to put it.  Our documentation states that if
$HOME/.gdbinit-<cpu> exists, it is read instead of $HOME/.gdbinit so I'll
just check for the file, source it and set inhibit_gdbinit if it's found.

Thanks for all the help.  It's interesting to hear from others about the
possible ramifications and alternate solutions to problems.

cheers,

Kris



      reply	other threads:[~2003-01-14 19:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 17:11 Kris Warkentin
2003-01-10 22:44 ` Felix Lee
2003-01-13 16:12   ` Kris Warkentin
2003-01-13 18:53     ` Andrew Cagney
2003-01-13 19:01       ` Kris Warkentin
2003-01-13 19:38         ` Andrew Cagney
2003-01-13 21:07           ` Kris Warkentin
2003-01-13 21:42             ` Andrew Cagney
2003-01-13 22:17               ` Kris Warkentin
2003-01-13 22:30                 ` Andrew Cagney
2003-01-14 19:11                   ` Kris Warkentin [this message]

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='000901c2bc00$aa564e80$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=ac131313@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=felix.1@canids.net \
    --cc=fnasser@redhat.com \
    --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