From: Andrew Cagney <ac131313@redhat.com>
To: Kris Warkentin <kewarken@qnx.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 19:38:00 -0000 [thread overview]
Message-ID: <3E2315B5.8030003@redhat.com> (raw)
In-Reply-To: <0e5301c2bb36$1002c400$0202040a@catdog>
> Kris,
>>
>> In the past there was a proposal (patch?) to add a configuration time
>> option that would specify a system init file. There was a patch. I
>> believe that the actual idea was accepted as sound but the patch was
>> lost in the paper trail :-( Can I suggest extending your patch so that
>> the mechanism and file are specified at configure time (please don't ask
>> me which of --with or --use or --... is the correct option :-).
>
>
> One problem with this (as Felix suggested earlier) is dealing with a gdb
> which supports multiple targets. The whole point is to be able to have
> per-target init files and hard wiring it in loses that. Specifying at
> config time would be okay for enable/disable but I think it would be better
> to have some sort of system of nomenclature for extra init files.
In this thread?
http://sources.redhat.com/ml/gdb/2002-12/msg00328.html
The proposal I'm refering to goes way back. It was something like:
--enable-system-gdbinit[=$DATAPREFIX/gdbinit]
That would make it possible to, for instance, to do things like load in
standard shared library paths. If a site really wants to add a site
specific configuration specific gdbinit file they can do that as well vis:
--enable-system-gdbinit=~/.gdbinit-TARGET --target=TARGET
> Here's a question: does a multi-targetted gdb know what it's targetting at
> the point of reading the .gdbinit or is this determined later? Is it
> switchable per session? I'm thinking that another possibility is to have it
> check for .gdbinit-$TARGET at the time that the target is determined.
To clarify something here, target and architecture are separate but very
related. GDB configured for a certain TARGET, will support one or more
architectures. The x86-64, for instance, also supports i386.
For a normal GDB session, an architecture will be selected twice. Once
for the default, and once based on the file that is loaded. The second
selection may occure before, during or after, .gdbinit parsing. The
`target' however, won't change.
Andrew
next prev parent reply other threads:[~2003-01-13 19:38 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 [this message]
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
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=3E2315B5.8030003@redhat.com \
--to=ac131313@redhat.com \
--cc=ezannoni@redhat.com \
--cc=felix.1@canids.net \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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