Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] -iex and -ix: Execute them _after_ gdbinits
Date: Sat, 16 Jun 2012 21:32:00 -0000	[thread overview]
Message-ID: <20120616213126.GA12840@host2.jankratochvil.net> (raw)
In-Reply-To: <83sjdvdkns.fsf@gnu.org>

On Sat, 16 Jun 2012 23:14:15 +0200, Eli Zaretskii wrote:
> My concern is about what happens before ~/.gdbinit is loaded, so
> nothing that happens after that can resolve that.

I do not understand which command would you want to run before ~/.gdbinit.
Real world ~/.gdbinit should only change settings or define new commands.


> > I have not found a use case where the current behavior is better.
> 
> It doesn't have to be better.  It has the advantage of being there
> first.  It's the new behavior that must have a significant advantage
> to justify an incompatible change of behavior.

The idea is that this is not a "change" as 7.4 did not have -iex at all.
-iex/-ix is a new feature for 7.5 so I am trying to make it right before it
becomes a standard.


> But setting auto-load is not the only thing I can do with -iex.  I can
> have any number of commands there which have nothing to do with
> safe-path and stuff.

It can affect only commands/settings which have some influence on the loading
of inferior.  There are not so many of such settings.

Besides safe-path also "set debug-file-directory" and associated "set
sysroot", not sure which more commands, if any.

"set debug-file-directory" - if set in /etc/gdbinit or ~/.gdbinit - currently
also cannot be overriden by -iex.


> We are removing a potentially useful feature for reasons that were not
> justified well enough.  Are there any reasons beyond the auto-load
> issue?  If not, I submit the reasons are not grave enough for the
> change, certainly not in a minor release.

[again]
The idea is that this is not a "change" as 7.4 did not have -iex at all.
-iex/-ix is a new feature for 7.5 so I am trying to make it right before it
becomes a standard.

auto-load general acceptance looks to be bad so far so I try to improve its
user visible interface as best as I can.


> And I don't see why we should pay so much attention to what Fedora
> does in its GDB distribution.

This is unrelated to Fedora.  If I looked at Fedora then I can say that the
current -iex/-ix is already an established standard and it cannot be changed
anymore.  I do track FSF gdb-7.5 release for this change.


> For example, I always build my own GDB, on any platform I work, and I don't
> see why I should be punished because Fedora does something.

I really do not understand meaning of this paragraph.  I specifically care
about FSF GDB release at this moment where the change in some way may
negatively affect F17 users where the current behavior is already deployed.

Still I do not think this change can anyhow negatively affect -iex use.


Thanks,
Jan


  reply	other threads:[~2012-06-16 21:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 19:54 Jan Kratochvil
2012-06-16 20:05 ` Eli Zaretskii
2012-06-16 20:13   ` Jan Kratochvil
2012-06-16 21:14     ` Eli Zaretskii
2012-06-16 21:32       ` Jan Kratochvil [this message]
2012-06-17  2:52         ` Eli Zaretskii
2012-06-17  6:50           ` Jan Kratochvil
2012-06-20 19:01             ` Jan Kratochvil
2012-06-20 19:38               ` Eli Zaretskii
2012-06-22  7:51                 ` Jan Kratochvil
2012-06-22  9:44                   ` Eli Zaretskii
2012-06-22 11:32                     ` Jan Kratochvil
2012-06-22 13:26                       ` Eli Zaretskii
2012-06-22 13:48                         ` Jan Kratochvil
2012-06-22 14:19                         ` Tom Tromey
2012-06-22 14:41                           ` Eli Zaretskii
2012-07-02 12:05                         ` [commit] " Jan Kratochvil
2012-06-22 14:18           ` Tom Tromey
2012-06-19  7:59         ` Doug Evans
2012-06-22 14:17   ` Tom Tromey
2012-06-18 16:45 ` Joel Brobecker
2012-06-22 14:17 ` Tom Tromey
2012-06-22 16:12   ` Joel Brobecker

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=20120616213126.GA12840@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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