From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: cbiesinger@google.com, tromey@adacore.com, brobecker@adacore.com,
gdb-patches@sourceware.org
Subject: Re: Building today's snapshot of GDB with MinGW
Date: Wed, 01 Jul 2020 18:20:40 +0300 [thread overview]
Message-ID: <83o8ozxnw7.fsf@gnu.org> (raw)
In-Reply-To: <56f26808-dfb0-6703-6f1f-9818c35946dd@polymtl.ca> (message from Simon Marchi on Tue, 30 Jun 2020 18:24:11 -0400)
I tried today "gdb --tui" on Windows 10, and was surprised to find
that it doesn't work: the debuggee fails to start when you type "run"
or "start". Windows pops up a dialog saying
The application was unable to start correctly (0xc0000142)
Click OK to close the application.
The application whose name is shown on the popup is the debuggee, but
the Windows Event Log shows a crash in the Windows console host.
This is not new, I see the same problem in all versions of GDB back to
7.9. It could be related to running a 32-bit debugger on 64-bit
Windows OS, though.
The only discussion of this that seems relevant is here:
https://github.com/msys2/MINGW-packages/issues/1744
I tried the workaround mentioned there with "set new-console on", and
it didn't work. The discussion further suggests to switch the Windows
console to the legacy mode, which I didn't try (because it affects all
console windows and requires restart AFAICT). This URL is from 4
years ago, so maybe the current builds of Windows 10 are different;
the version I tried this on is build 18362.836.
Did anyone try running "gdb --tui" on Windows 10 console, and if so,
did that work for you?
next prev parent reply other threads:[~2020-07-01 15:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 18:27 Eli Zaretskii
2020-06-29 20:36 ` Christian Biesinger
2020-06-30 14:09 ` Eli Zaretskii
2020-06-30 22:24 ` Simon Marchi
2020-07-01 15:09 ` Eli Zaretskii
2020-07-02 13:50 ` Eli Zaretskii
2020-07-02 14:25 ` Simon Marchi
2020-07-02 14:30 ` Simon Marchi
2020-07-02 17:47 ` Eli Zaretskii
2020-07-02 14:40 ` Pedro Alves
2020-07-02 17:46 ` Eli Zaretskii
2020-07-02 18:21 ` Pedro Alves
2020-07-02 18:33 ` Eli Zaretskii
2020-07-02 18:34 ` Pedro Alves
2020-07-01 15:20 ` Eli Zaretskii [this message]
2020-07-01 19:25 ` Christian Biesinger
2020-07-02 2:29 ` Eli Zaretskii
2020-07-02 10:18 ` Hannes Domani
2020-07-02 13:20 ` Eli Zaretskii
2020-07-06 10:39 ` Hannes Domani
2020-07-06 16:35 ` Eli Zaretskii
2020-07-01 19:25 ` Joel Brobecker
2020-07-02 13:46 ` Eli Zaretskii
2020-06-30 16:18 ` Eli Zaretskii
2020-06-30 18:21 ` Christian Biesinger
2020-06-30 18:28 ` Eli Zaretskii
2020-07-01 19:29 ` Joel Brobecker
2020-07-02 2:31 ` Eli Zaretskii
2020-07-01 19:30 ` Joel Brobecker
2020-07-02 13:39 ` Eli Zaretskii
2020-07-03 15:25 ` Joel Brobecker
2020-07-27 9:49 ` Tom de Vries
2020-07-27 10:05 ` Tom de Vries
2020-07-27 10:26 ` Tom de Vries
2020-07-27 11:48 ` [committed][gdb/build] Fix typo sys/sockets.h -> sys/socket.h Tom de Vries
2020-07-27 12:51 ` Joel Brobecker
2020-07-27 14:18 ` Building today's snapshot of GDB with MinGW Eli Zaretskii
2020-07-02 14:12 ` Eli Zaretskii
2020-07-03 15:08 ` 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=83o8ozxnw7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tromey@adacore.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