unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: merrick@luois.me
Cc: 54051@debbugs.gnu.org
Subject: bug#54051: 29.0.50; latest master build with lucid crashes
Date: Fri, 18 Feb 2022 13:32:28 +0800	[thread overview]
Message-ID: <878ru8spsj.fsf@yahoo.com> (raw)
In-Reply-To: <87wnhsc0nv.fsf@lagann.mail-host-address-is-not-set> (merrick@luois.me's message of "Fri, 18 Feb 2022 11:29:40 +0800")

merrick@luois.me writes:

> Unfortunately I can't get backtrace from `./src/emacs -q -xrm
> 'Emacs.synchronous: true' since it hangs forever after doing the above
> steps.

If it hangs, you should attach gdb to that emacs and print a backtrace
from there.

Thanks.

> Here is backtrace from running `gdb --args ./src/emacs -Q`:
> https://pastebin.com/UmBNMwC1

Please don't use pastebin in the future, since it's not convenient for
me to open those links.  Instead, just send the backtrace in the email
to the bug tracker.

But a backtrace from an X error that wasn't created from in synchronous
mode is completely useless for debugging, so please see what I wrote
above.





  reply	other threads:[~2022-02-18  5:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  3:29 bug#54051: 29.0.50; latest master build with lucid crashes merrick--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18  5:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-18  8:12 ` Eli Zaretskii
2022-02-18 12:42   ` A.I. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21  5:51     ` A.I. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 10:09       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 11:41         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-23  2:59           ` A.I. via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-23  3:45             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=878ru8spsj.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54051@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=merrick@luois.me \
    /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).