Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Hannes Domani <ssbssa@yahoo.de>,
	Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Implement debugging of WOW64 processes in gdbserver
Date: Wed, 29 Apr 2020 11:09:08 -0400	[thread overview]
Message-ID: <a777ea78-48d6-b295-6292-fcf50584df5a@simark.ca> (raw)
In-Reply-To: <471105047.4011567.1588157665165@mail.yahoo.com>

On 2020-04-29 6:54 a.m., Hannes Domani via Gdb-patches wrote:
>> Since this is copied from gdb/windows-nat.c, it would be nice to factor it
>> out (as well as the small snippet below), so it can be shared.  Otherwise,
>> if we make a fix to one, we'll most likely forget to fix the other.
>>
>> The shared versions would go into gdb/nat/windows-nat.c.
> 
> There might be even more code that can be shared now, I planned to do this
> with a later patch.

Ok.

>> Why do we need to get these functions like this, instead of just calling them?
> 
> These functions are not available on WinXP, and the extra check for them
> was actually the reason of this v2:
> 
> +  if (wow64_process
> +      && (win32_Wow64SuspendThread == nullptr
> +      || win32_Wow64GetThreadContext == nullptr
> +      || win32_Wow64SetThreadContext == nullptr))
> +    error ("WOW64 debugging is not supported on this system.\n");

Ok, please add a comment to that effect then.  This way if we decide we no longer want
to support Windows XP, we can remove this in favor of just calling the functions directly.

Simon


  reply	other threads:[~2020-04-29 15:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200427133416.9314-1-ssbssa.ref@yahoo.de>
2020-04-27 13:34 ` Hannes Domani
2020-04-28 15:53   ` Simon Marchi
2020-04-29 10:54     ` Hannes Domani
2020-04-29 15:09       ` Simon Marchi [this message]
2020-04-29 15:16         ` Eli Zaretskii
2020-04-29 15:28           ` Simon Marchi
2020-04-29 16:05             ` 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=a777ea78-48d6-b295-6292-fcf50584df5a@simark.ca \
    --to=simark@simark.ca \
    --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