From: "Hannes Domani via gdb-patches" <gdb-patches@sourceware.org>
To: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Implement debugging of WOW64 processes
Date: Tue, 03 Mar 2020 21:12:00 -0000 [thread overview]
Message-ID: <140963475.6133151.1583269956021@mail.yahoo.com> (raw)
In-Reply-To: <cfdaa0b9-7401-3f1d-dcdd-38b81532e5ee@simark.ca>
Am Dienstag, 3. März 2020, 22:01:00 MEZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:
> On 2020-03-03 3:28 p.m., Eli Zaretskii wrote:
> >> Cc: gdb-patches@sourceware.org
> >> From: Simon Marchi <simark@simark.ca>
> >> Date: Tue, 3 Mar 2020 14:36:53 -0500
> >>
> >> Eli, just wondering, did you review the code parts of this patch?
> >
> > I've read it, yes. I cannot say I know this area of Windows APIs well
> > enough to say something intelligent, though. If the patch was tested
> > with 32-bit programs, I think it's OK.
>
> OK, thanks. I've been looking at these Windows patches because nobody else
> was reviewing them. I don't mind keeping doing that, but keep in mind that
> I don't know Windows nearly as much as you, so I really appreciate that you
> take a look.
>
> I looked at this patch quickly, it seems to add some code duplication and
> complexity, but that looks difficult to avoid without some serious refactoring
> (which would of course be nice, but not required for adding this feature).
I'm not very fond of the code duplication either.
The only way I can think of, is to refactor it into template functions that
can accept both CONTEXT or WOW64_CONTEXT.
Is this what you had in mind also, or do you have a better idea?
> The only bit I don't particularly like is the inclusion of i386-windows-nat.c
> in amd64-windows-nat.c, that just seems weird, and not very good in a long term
> maintenance perspective.
>
> Can you instead include the i386-windows-nat.c file in the cygwin64 and mingw64
> builds (in configure.nat), so that it gets compiled in a more standard fashion?
Yes, I can do that.
I didn't even know that configure.nat was the place for this, that's why I
did it with the include.
Regards
Hannes Domani
next prev parent reply other threads:[~2020-03-03 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200303182057.8973-1-ssbssa.ref@yahoo.de>
2020-03-03 18:21 ` Hannes Domani via gdb-patches
2020-03-03 18:51 ` Eli Zaretskii
2020-03-03 19:12 ` Hannes Domani via gdb-patches
2020-03-03 19:30 ` Eli Zaretskii
2020-03-03 19:36 ` Simon Marchi
2020-03-03 20:28 ` Eli Zaretskii
2020-03-03 21:01 ` Simon Marchi
2020-03-03 21:12 ` Hannes Domani via gdb-patches [this message]
2020-03-03 21:31 ` Simon Marchi
2020-03-04 3:33 ` Eli Zaretskii
2020-03-13 18:16 ` Tom Tromey
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=140963475.6133151.1583269956021@mail.yahoo.com \
--to=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