public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ssbssa@yahoo.de, gdb-patches@sourceware.org
Subject: Re: [PATCH] Implement debugging of WOW64 processes
Date: Tue, 03 Mar 2020 21:01:00 -0000	[thread overview]
Message-ID: <cfdaa0b9-7401-3f1d-dcdd-38b81532e5ee@simark.ca> (raw)
In-Reply-To: <83wo81w5cu.fsf@gnu.org>

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).

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?

Simon

  reply	other threads:[~2020-03-03 21:01 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 [this message]
2020-03-03 21:12               ` Hannes Domani via gdb-patches
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=cfdaa0b9-7401-3f1d-dcdd-38b81532e5ee@simark.ca \
    --to=simark@simark.ca \
    --cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).