Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@yahoo.de>
To: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/7] Handle Windows drives in auto-load script paths
Date: Tue, 26 May 2020 17:14:21 +0000 (UTC)	[thread overview]
Message-ID: <445485904.6616560.1590513261197@mail.yahoo.com> (raw)
In-Reply-To: <CAPTJ0XFWMsYhCstGjSj=WJG8wvSDebrquryzaE6ezMgOPekP2w@mail.gmail.com>

 Am Dienstag, 26. Mai 2020, 18:43:15 MESZ hat Christian Biesinger <cbiesinger@google.com> Folgendes geschrieben:

> On Tue, May 26, 2020 at 11:40 AM Hannes Domani via Gdb-patches
> <gdb-patches@sourceware.org> wrote:
> >
> >  Am Dienstag, 26. Mai 2020, 18:32:38 MESZ hat Christian Biesinger <cbiesinger@google.com> Folgendes geschrieben:
> >
> > > On Tue, May 26, 2020 at 11:25 AM Hannes Domani via Gdb-patches
> > > <gdb-patches@sourceware.org> wrote:
> > > >
> > > >  Am Dienstag, 26. Mai 2020, 18:05:57 MESZ hat Christian Biesinger <cbiesinger@google.com> Folgendes geschrieben:
> > > >
> > > > > On Mon, May 25, 2020 at 1:57 PM Hannes Domani via Gdb-patches
> > > > > <gdb-patches@sourceware.org> wrote:
> > > > > >
> > > > > > Fixes this testsuite fail on Windows:
> > > > > > FAIL: gdb.base/auto-load.exp: print $script_loaded
> > > > > >
> > > > > > Converts the debugfile path from c:/dir/file to /c/dir/file, so it can be
> > > > > > appended to the auto-load path.
> > > > >
> > > > > How does this work? I thought /c/foo was not supported by either
> > > > > cygwin or mingw?
> > > >
> > > > Yes, but in this case we need a path that can be appended to the various
> > > > entries of 'set auto-load scripts-directory'.
> > > > c:/foo can't be appended, but /c/foo can.
> > > > So you would get something like c:/script/directory/c/foo.
> > >
> > > OK, so I *think* what you're saying is that if you have an objfile
> > > c:\foo\bar.dll, and an auto-load directory c:\load, then with this
> > > patch we will look for an auto-load script in
> > > c:\load\c\foo\bar.dll-gdb.py? Is that right?
> >
> > Basically, yes.
> >
> >
> > > If so, shouldn't there be a documentation update about how this works
> > > on Windows, and possibly a NEWS entry?
> >
> > A news entry that the bug was fixed?
> > From how I understand gdb.base/auto-load.exp, this is the way it was always
> > supposed to work (did I understand this wrong?).
>
> I don't feel so strongly about NEWS, but I specifically meant the
> translation of c:\ to c/ on Windows -- shouldn't that be documented?

That's probably a good idea, debug-file-directory works the same way, and
there it is documented like this:

(On MS-Windows/MS-DOS, the drive letter of the executable’s leading
directories is converted to a one-letter subdirectory, i.e. d:/usr/bin/ is
converted to /d/usr/bin/, because Windows filesystems disallow colons in file
names.)

I will add something similar for scripts-directory.


Hannes


  reply	other threads:[~2020-05-26 17:14 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200525185659.59346-1-ssbssa.ref@yahoo.de>
2020-05-25 18:56 ` Windows testsuite failures Hannes Domani
2020-05-25 18:56   ` [PATCH 1/7] Fix function argument and return value locations Hannes Domani
2020-05-25 21:02     ` Simon Marchi
2020-05-25 21:32       ` Hannes Domani
2020-05-25 22:14         ` Simon Marchi
2020-05-25 23:03           ` Hannes Domani
2020-05-26 16:14             ` Simon Marchi
2020-05-26 20:43         ` Tom Tromey
2020-05-25 18:56   ` [PATCH 2/7] Handle Windows drives in auto-load script paths Hannes Domani
2020-05-26 16:04     ` Jon Turney
2020-05-26 16:31       ` Hannes Domani
2020-05-26 16:05     ` Christian Biesinger
2020-05-26 16:25       ` Hannes Domani
2020-05-26 16:31         ` Christian Biesinger
2020-05-26 16:40           ` Hannes Domani
2020-05-26 16:42             ` Christian Biesinger
2020-05-26 17:14               ` Hannes Domani [this message]
2020-05-25 18:56   ` [PATCH 3/7] Handle Windows drives in rbreak paths Hannes Domani
2020-05-25 18:56   ` [PATCH 4/7] Use errno value of first openp failure Hannes Domani
2020-05-26 20:37     ` Tom Tromey
2020-05-25 18:56   ` [PATCH 5/7] Close file handle of empty history file Hannes Domani
2020-05-26 16:37     ` Christian Biesinger
2020-05-26 17:42       ` Hannes Domani
2020-05-27 14:33         ` Tom Tromey
2020-05-27 17:37           ` Hannes Domani
2020-05-27 18:27             ` Christian Biesinger
2020-05-25 18:56   ` [PATCH 6/7] Move exit_status_set_internal_vars out of GLOBAL_CURDIR Hannes Domani
2020-05-26 20:45     ` Tom Tromey
2020-05-27 17:50       ` Hannes Domani
2020-05-25 18:56   ` [PATCH 7/7] Reset Windows hardware breakpoints on executable's entry point Hannes Domani
2020-05-27 12:07     ` Pedro Alves
2020-05-27 14:48       ` Pedro Alves
2020-05-27 15:39         ` Hannes Domani
2020-05-31 15:54           ` Pedro Alves
2020-05-31 16:37     ` Pedro Alves
2020-06-07 12:56       ` Hannes Domani
2020-07-08 17:43         ` Hannes Domani
2020-10-09 18:22         ` Pedro Alves
2020-10-09 18:51           ` Hannes Domani via Gdb-patches
2020-10-12 11:13             ` Pedro Alves
2020-10-12 17:21       ` Tom Tromey
2020-10-12 17:22         ` Tom Tromey
2020-05-28 18:15   ` Windows testsuite failures Christian Biesinger
2020-05-28 18:37     ` Hannes Domani

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=445485904.6616560.1590513261197@mail.yahoo.com \
    --to=ssbssa@yahoo.de \
    --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