From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 53954@debbugs.gnu.org
Subject: bug#53954: 29.0.50; segmentation fault, Februray 12th 2022
Date: Sat, 12 Feb 2022 14:37:30 +0200 [thread overview]
Message-ID: <837da0s1kl.fsf@gnu.org> (raw)
In-Reply-To: <86v8xkfgsc.fsf@protected.rcdrun.com> (message from Jean Louis on Sat, 12 Feb 2022 14:47:15 +0300)
tags 53954 moreinfo
thanks
> From: Jean Louis <bugs@gnu.support>
> Date: Sat, 12 Feb 2022 14:47:15 +0300
>
> I have updated today with `git pull' to latest and found that I cannot
> execute Emacs, there is segmentation fault.
>
> Attached file error.txt lists errors when running `emacs'.
>
> Attached file error2.txt lists errors when running `emacs -Q'.
Thanks, but these files can only be interpreted on your system, see
the node "Crashing" in the Emacs manual for how to do that. better
yet, run the problematic executable under GDB, and show the backtrace
from the crash as GDB displays it.
> I have reverted to 5th February 2022, to random commit, that I can run
> Emacs, otherwise I cannot.
Please provide the additional information mentioned above regarding
the faulty executable, otherwise we will be unable to work on this
problem.
> In GNU Emacs 29.0.50 (build 5, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.4, Xaw3d scroll bars)
> of 2022-02-12 built on protected.rcdrun.com
> Repository revision: 686f7f8f628c04e9d574186173165b2b5a9f92e2
I'm guessing this is not the version of the faulty executable.
next prev parent reply other threads:[~2022-02-12 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 11:47 bug#53954: 29.0.50; segmentation fault, Februray 12th 2022 Jean Louis
2022-02-12 12:37 ` Eli Zaretskii [this message]
2022-02-12 21:10 ` Jean Louis
2022-02-12 21:13 ` Jean Louis
2022-02-12 21:27 ` Jean Louis
2022-02-13 0:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-13 7:59 ` Jean Louis
2022-02-13 8:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-13 20:33 ` Lars Ingebrigtsen
2022-02-12 21:39 ` Jean Louis
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=837da0s1kl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53954@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).