From: Hannes Domani <ssbssa@yahoo.de>
To: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Implement debugging of WOW64 processes in gdbserver
Date: Sun, 26 Apr 2020 16:53:53 +0000 (UTC) [thread overview]
Message-ID: <545110470.974890.1587920033486@mail.yahoo.com> (raw)
In-Reply-To: <83h7x8alys.fsf@gnu.org>
Am Sonntag, 26. April 2020, 18:32:28 MESZ hat Eli Zaretskii <eliz@gnu.org> Folgendes geschrieben:
> > Date: Fri, 24 Apr 2020 17:59:44 +0200
> > From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
> >
> > +#ifdef __x86_64__
> > + if (wow64_process)
> > + ok = (*win32_EnumProcessModulesEx) (current_process_handle,
> > + DllHandle,
> > + sizeof (HMODULE),
> > + &cbNeeded,
> > + LIST_MODULES_32BIT);
>
> If win32_EnumProcessModulesEx is a NULL point (i.e. its load from the
> DLL failed, because we are on an older Windows version), the above
> will segfault, no? Do we want to support WOW64 debugging on systems
> older than Vista?
Good question.
I've never actually seen/used a 64bit WinXP, so I didn't even consider this
case.
According to the microsoft docs, Wow64GetThreadContext/Wow64SetThreadContext/
Wow64SuspendThread are also available from Vista upwards, so WOW64 debugging
is impossible on XP.
Should I error() in do_initial_(windows|child)_stuff for WOW64 processes if any
of the functions is missing?
next prev parent reply other threads:[~2020-04-26 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200424155944.17332-1-ssbssa.ref@yahoo.de>
2020-04-24 15:59 ` Hannes Domani
2020-04-24 16:26 ` Eli Zaretskii
2020-04-26 16:53 ` Hannes Domani [this message]
2020-04-26 17:14 ` 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=545110470.974890.1587920033486@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