Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 7.5: Problems with the auto-load safe-path feature
Date: Mon, 20 Aug 2012 16:36:00 -0000	[thread overview]
Message-ID: <837gstcyi2.fsf@gnu.org> (raw)
In-Reply-To: <20120820150725.GA2310@host2.jankratochvil.net>

> Date: Mon, 20 Aug 2012 17:07:25 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
> 
> On Sat, 18 Aug 2012 19:07:49 +0200, Eli Zaretskii wrote:
> > Like in the patch below?  I can drop the #ifdef, if no one objects (it
> > could surprise Unix users who call their programs FOO.exe for some
> > reason).
> 
> Yes, Joel also was for dropping the #ifdef.
> 
> Also I believe GDB should test the .exe-less filenames even
> in 'set auto-load scripts-directory' entries.
> 
> What about the patch below?

Looks good to me, thanks.


  reply	other threads:[~2012-08-20 16:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18 12:32 Eli Zaretskii
2012-08-18 13:21 ` Jan Kratochvil
2012-08-18 15:01   ` Eli Zaretskii
2012-08-18 16:19     ` Joel Brobecker
2012-08-18 17:11       ` Eli Zaretskii
2012-08-20 14:54   ` Tom Tromey
2012-08-27 16:48   ` [commit+7.5] apropos fix for auto-load texts [Re: GDB 7.5: Problems with the auto-load safe-path feature] Jan Kratochvil
2012-08-18 16:11 ` GDB 7.5: Problems with the auto-load safe-path feature Joel Brobecker
2012-08-18 17:07   ` Eli Zaretskii
2012-08-20 15:08     ` Jan Kratochvil
2012-08-20 16:36       ` Eli Zaretskii [this message]
2012-08-27 16:53       ` [commit+7.5] auto-load for .exe files [Re: GDB 7.5: Problems with the auto-load safe-path feature] Jan Kratochvil

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=837gstcyi2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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