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 v2] Fix WOW64 process system DLL paths
Date: Thu, 26 Mar 2020 20:48:35 +0000 (UTC)	[thread overview]
Message-ID: <1525100081.5445433.1585255715401@mail.yahoo.com> (raw)
In-Reply-To: <CAPTJ0XG_YRzrvx1nmY=PBrUtA5rYgEqBPOa-rAhOQGLzb5s0JA@mail.gmail.com>

 Am Donnerstag, 26. März 2020, 21:39:27 MEZ hat Christian Biesinger <cbiesinger@google.com> Folgendes geschrieben:

> On Thu, Mar 26, 2020 at 3:35 PM Hannes Domani via Gdb-patches
>
> <gdb-patches@sourceware.org> wrote:
> >
> >  Am Donnerstag, 26. März 2020, 20:26:14 MEZ hat Eli Zaretskii <eliz@gnu.org> Folgendes geschrieben:
> >
> > > > Date: Wed, 25 Mar 2020 14:35:51 +0000 (UTC)
> > >
> > > > From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
> > > >
> > > > > > But I figured my way with GetSystemWow64Directory is simpler.
> > > > > >
> > > > > >
> > > > > > Is the v2 OK to commit?
> > > > >
> > > > > Yes, thanks.
> > > >
> > > > Pushed, thanks.
> > >
> > >
> > > It looks like the same problem exists in the 32-bit Windows build of
> > > GDB, when it runs on 64-bit Windows 10: "info sharedlibrary" shows
> > > C:\Windows\system32 instead of C:\Windows\SysWOW64 (it doesn't happen
> > > on 64-bit Windows 7, for example).  So I guess the code which replaces
> > > the former with the latter should also be in the 32-bit build, not
> > > just "#ifdef __x86_64__".
> >
> > Yes, for me (on Win7) it also happens with the same dlls in the 32-bit gdb
> > as with the 64-bit gdb.
> > But it shouldn't matter, since for 32-bit gdb all C:\Windows\system32 paths
> > are automatically redirected[1] to C:\Windows\SysWOW64 anyways.
> >
> > [1] https://docs.microsoft.com/en-us/windows/win32/winprog64/file-system-redirector
>
>
> Even so, it's probably less confusing for the user if what GDB
> displays actually matches reality?

I guess you are right.
I will prepare a patch for this.


Hannes


  reply	other threads:[~2020-03-26 20:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200324192351.3904-1-ssbssa.ref@yahoo.de>
2020-03-24 19:23 ` Hannes Domani
2020-03-24 22:10   ` Simon Marchi
2020-03-24 23:56   ` Jon Turney
2020-03-25  0:44     ` Hannes Domani
2020-03-25 14:04   ` Simon Marchi
2020-03-25 14:22     ` Hannes Domani
2020-03-25 14:23       ` Simon Marchi
2020-03-25 14:35         ` Hannes Domani
2020-03-26 19:08           ` Eli Zaretskii
2020-03-26 20:35             ` Hannes Domani
2020-03-26 20:38               ` Christian Biesinger
2020-03-26 20:48                 ` Hannes Domani [this message]
2020-03-26 20:56                   ` Simon Marchi
2020-03-26 21:01                     ` Hannes Domani
2020-03-26 22:10                       ` Simon Marchi
2020-03-27  7:00                   ` Eli Zaretskii
2020-03-27  6:57               ` Eli Zaretskii

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=1525100081.5445433.1585255715401@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