From: Eli Zaretskii <eliz@gnu.org>
To: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: gdb fails to flush output (msys2)
Date: Tue, 15 Mar 2022 18:47:02 +0200 [thread overview]
Message-ID: <83ilsfi2nt.fsf@gnu.org> (raw)
In-Reply-To: <865yofb7nq.fsf@csic.es> (juanjose.garciaripoll@gmail.com)
> From: Juan José García-Ripoll
> <juanjose.garciaripoll@gmail.com>
> Date: Tue, 15 Mar 2022 15:40:57 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
> > You didn't answer my question about where you downloaded this GDB. Is
> > this the "usual" MSYS2 GDB, and if so, is it linked against UCRT or
> > the "normal" MSVCRT runtime?
>
> I have used both the UCRT and MSVCRT runtimes, provided in
> c:/msys64/ucrt64/bin/gdb.exe and c:/msys64/mingw64/bin/gdb.exe They are
> downloaded from the MSYS2 terminal using pacman, so I assume they are
> from the standard repositories.
And they both exhibit the same problematic behavior?
But actually the problematic behavior is of the program you are
debugging, right? Is that one linked against UCRT or MSVCRT?
next prev parent reply other threads:[~2022-03-15 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 11:18 gdb fails to flush output (msys2) Juan José García-Ripoll
2022-03-14 13:33 ` Eli Zaretskii
2022-03-14 17:55 ` Juan José García-Ripoll
2022-03-14 18:23 ` Eli Zaretskii
2022-03-14 18:40 ` Eli Zaretskii
2022-03-15 9:58 ` Juan José García-Ripoll
2022-03-15 11:48 ` Jostein Kjønigsen
2022-03-15 13:24 ` Juan José García-Ripoll
2022-03-15 13:33 ` Juan José García-Ripoll
2022-03-15 14:34 ` Eli Zaretskii
2022-03-15 14:40 ` Juan José García-Ripoll
2022-03-15 16:47 ` Eli Zaretskii [this message]
2022-03-15 17:38 ` Juan José García-Ripoll
2022-03-15 17:56 ` Eli Zaretskii
2022-03-15 15:12 ` Juan José García-Ripoll
2022-03-15 16:53 ` Eli Zaretskii
2022-03-15 14:25 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ilsfi2nt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juanjose.garciaripoll@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).