From: Eli Zaretskii <eliz@gnu.org>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: mingw-w64's GDB 64-bit/32-bit debugging
Date: Tue, 06 Dec 2016 03:34:00 -0000 [thread overview]
Message-ID: <83bmwpk9y2.fsf@gnu.org> (raw)
In-Reply-To: <6b0e1474-b965-ef37-bd0f-3b38aad07810@codesourcery.com> (message from Luis Machado on Mon, 5 Dec 2016 20:36:50 -0600)
> From: Luis Machado <lgustavo@codesourcery.com>
> Date: Mon, 5 Dec 2016 20:36:50 -0600
>
> Is a native mingw-w64 gdb capable of debugging 64-bit and 32-bit Windows
> processes or do we need a 32-bit gdb for a 32-bit process and a 64-bit
> gdb for a 64-bit process?
The latter, I'm afraid.
> Doing some tests i noticed ming-w64's 64-bit GDB doesn't quite like the
> 32-bit executable, choking on some 64-bit Windows symbol files and
> eventually getting an unexpected signal.
Yes, GDB doesn't yet have code that implements the protocol for
debugging WOW64 applications, and the unexpected and unhandled
exception you see is a sign of that. I'm quite sure patches to that
effect will be appreciated.
prev parent reply other threads:[~2016-12-06 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 2:37 Luis Machado
2016-12-06 3:34 ` Eli Zaretskii [this message]
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=83bmwpk9y2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=lgustavo@codesourcery.com \
/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