From: Eli Zaretskii <eliz@gnu.org>
To: Akib Azmain Turja <akib@disroot.org>
Cc: 59340@debbugs.gnu.org
Subject: bug#59340: 29.0.50; Latest Emacs from master gives various native compilation errors
Date: Fri, 18 Nov 2022 18:56:39 +0200 [thread overview]
Message-ID: <83o7t49p6g.fsf@gnu.org> (raw)
In-Reply-To: <87cz9kti2z.fsf@disroot.org> (message from Akib Azmain Turja on Fri, 18 Nov 2022 21:09:40 +0600)
> From: Akib Azmain Turja <akib@disroot.org>
> Cc: 59340@debbugs.gnu.org
> Date: Fri, 18 Nov 2022 21:09:40 +0600
>
> However, why the crash? Is it somehow because the old eln get loaded?
To answer that, I'd need to see a backtrace from the crash. Run Emacs
under GDB and produce the backtrace when Emacs crashes, then post it
here. (I hope your Emacs is not stripped of debug symbols, otherwise
the backtrace will not be useful.)
next prev parent reply other threads:[~2022-11-18 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 19:08 bug#59340: 29.0.50; Latest Emacs from master gives various native compilation errors Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 20:04 ` Eli Zaretskii
2022-11-18 9:01 ` Andrea Corallo
2022-11-18 11:23 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-18 11:39 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-18 12:06 ` Eli Zaretskii
2022-11-18 15:09 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-18 15:12 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-18 16:28 ` Robert Pluim
2022-11-18 16:56 ` Eli Zaretskii [this message]
2022-11-18 20:06 ` Andrea Corallo
2022-11-19 4:23 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-22 17:00 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-24 18:27 ` Stefan Kangas
2023-06-05 22:17 ` Andrea Corallo
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=83o7t49p6g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59340@debbugs.gnu.org \
--cc=akib@disroot.org \
/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).