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: Mon, 13 Jan 2003 22:17:00 -0000	[thread overview]
Message-ID: <0ed601c2bb51$818e58d0$0202040a@catdog> (raw)
In-Reply-To: <3E2332A5.10403@redhat.com>

>
> Er, that is a single gdb executable supporting ``multiple architectures''.
>

Well then a configure option isn't the answer.  We build GDBs targetting 5
different CPUs.  At the moment, these are separate binaries so it's an easy
matter to have each binary look for a hard-wired $HOME/.gdbinit-nto<CPU>.
Someday, however, we want to multi-arch gdb (as we already have with
binutils) so that we can ship one gdb binary.  That is where the
configure/compile time setting of the extra gdbinit file falls apart.  What
I was asking about earlier was a runtime method of determining the file to
source so that if I use the same binary for multiple targets, I can source a
different file for each one.

I was thinking that we should put a hook in the code that is run when
switching targets to source a target file based on what gdb thinks its
target is at the time.

cheers,

Kris


  reply	other threads:[~2003-01-13 22:17 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 [this message]
2003-01-13 22:30                 ` Andrew Cagney
2003-01-14 19:11                   ` Kris Warkentin

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='0ed601c2bb51$818e58d0$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