public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>, Hannes Domani <ssbssa@yahoo.de>
Cc: gdb-patches@sourceware.org
Subject: Building GDB 15.0.91 on MinGW: Problem with TUI
Date: Fri, 07 Jun 2024 16:13:55 +0300	[thread overview]
Message-ID: <867cf0gajw.fsf@gnu.org> (raw)
In-Reply-To: <20240601155907.B796C81691@takamaka.gnat.com> (message from Joel Brobecker on Sat, 1 Jun 2024 08:59:07 -0700 (PDT))

After I've succeeded to build this pretest, I've bumped into a problem
with debugging using TUI (which uses ncurses in my build).  GDB starts
okay with the -tui option, but running the debuggee fails, popping a
Windows dialog that says:

    The application was unable to start correctly (0xc0000142).
    Click OK to close the application

The same happens with GDB 14.1, so this is not new.

According to this page:

https://github.com/msys2/MINGW-packages/issues/1744#issuecomment-256146266

the problem is with the newly-redesigned Windows Console in Windows 10
and 11, and the solution is either (a) use "set new-console 1" (to
direct the output of the debuggee to a separate console), or (b) turn
on the "Use legacy console" option of the Windows terminal.

I've successfully used "set new-console 1" (and would assume the
other solution also works, although I haven't tried), but are there
other, more convenient solutions for this?  Perhaps some change in
ncurses or in how GDB handles the debuggee output in this case?

Hannes, do you know anything about this?

Thanks.

  parent reply	other threads:[~2024-06-07 13:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-01 15:59 GDB 15.0.91 available for testing Joel Brobecker
2024-06-06 20:16 ` Building GDB 15.0.91 on MinGW: CPPFLAGS Eli Zaretskii
2024-06-07 12:21   ` Building GDB 15.0.91 on MinGW: CPPFLAGS and libctf Eli Zaretskii
     [not found]     ` <87r0d8k0gc.fsf@tromey.com>
2024-06-07 19:56       ` Eli Zaretskii
2024-06-07 21:39         ` Tom Tromey
2024-06-08  6:10           ` Eli Zaretskii
2024-06-08  7:54     ` Eli Zaretskii
2024-06-06 20:20 ` Building GDB 15.0.91 on MinGW: gcore.c Eli Zaretskii
     [not found]   ` <87msnwk0du.fsf@tromey.com>
2024-06-08  7:25     ` Eli Zaretskii
2024-06-07 12:27 ` Building GDB 15.0.91 on MinGW: ui_out_emit_type<ui_out_type_tuple>::m_uiout Eli Zaretskii
     [not found]   ` <87ikykk07l.fsf@tromey.com>
2024-06-07 19:57     ` Eli Zaretskii
2024-06-07 12:34 ` Building GDB 15.0.91 on MinGW: libctf.la Eli Zaretskii
2024-06-08  7:56   ` Eli Zaretskii
2024-06-07 13:13 ` Eli Zaretskii [this message]
     [not found]   ` <599928735.5136862.1717766505896@mail.yahoo.com>
2024-06-07 13:48     ` Building GDB 15.0.91 on MinGW: Problem with TUI 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=867cf0gajw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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).