From: Eli Zaretskii <eliz@gnu.org>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Fix WOW64 process system DLL paths
Date: Thu, 26 Mar 2020 21:08:10 +0200 [thread overview]
Message-ID: <831rpf9bol.fsf@gnu.org> (raw)
In-Reply-To: <30076034.3775038.1585146951973@mail.yahoo.com> (message from Hannes Domani via Gdb-patches on Wed, 25 Mar 2020 14:35:51 +0000 (UTC))
> 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__".
next prev parent reply other threads:[~2020-03-26 19:08 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 [this message]
2020-03-26 20:35 ` Hannes Domani
2020-03-26 20:38 ` Christian Biesinger
2020-03-26 20:48 ` Hannes Domani
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=831rpf9bol.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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