From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: luangruo@yahoo.com, 53377@debbugs.gnu.org
Subject: bug#53377: 28.0.91: Build fails on MSYS2/MinGW-w64 with Clang
Date: Thu, 20 Jan 2022 09:54:35 +0200 [thread overview]
Message-ID: <83lezargec.fsf@gnu.org> (raw)
In-Reply-To: <87r1936oqs.fsf@telefonica.net> (message from Óscar Fuentes on Thu, 20 Jan 2022 04:59:55 +0100)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Thu, 20 Jan 2022 04:59:55 +0100
> Cc: 53377@debbugs.gnu.org
>
> Besides, Clang has its own debugger.
Last time I looked, the LLVM debugger didn't work well on Windows, and
was definitely not a good idea as a tool to debug Emacs, because it
didn't support the .gdbinit commands (which are essential for any
reasonable debugging of the Emacs C code), and didn't support GDB/MI
(which means you cannot use it with "M-x gdb" from Emacs).
Unless this has changed drastically since I looked, my advice to you
is to use GDB for debugging the Emacs C code, otherwise you will have
a whole additional level of difficulties in making this port happen.
next prev parent reply other threads:[~2022-01-20 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 23:41 bug#53377: 28.0.91: Build fails on MSYS2/MinGW-w64 with Clang Óscar Fuentes
2022-01-20 1:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 3:32 ` Óscar Fuentes
2022-01-20 3:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 3:59 ` Óscar Fuentes
2022-01-20 4:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 7:54 ` Eli Zaretskii [this message]
2022-01-20 7:40 ` Eli Zaretskii
2022-01-21 4:14 ` Richard Stallman
2022-01-20 7:33 ` 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=83lezargec.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53377@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=ofv@wanadoo.es \
/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).