unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gilles <gilles.usenet@gmail.com>
Cc: 47334@debbugs.gnu.org
Subject: bug#47334: 27.1; Incompatibility between daemon, desktop and highlight-changes-mode
Date: Tue, 23 Mar 2021 12:06:59 +0200	[thread overview]
Message-ID: <83h7l289q4.fsf@gnu.org> (raw)
In-Reply-To: <CAHf9+Cs7P-r7ESv4LJG6Y6KHENfH_Qcjq9hdrVkpvVcyUvJsJw@mail.gmail.com> (message from Gilles on Tue, 23 Mar 2021 01:30:36 +0100)

> From: Gilles <gilles.usenet@gmail.com>
> Date: Tue, 23 Mar 2021 01:30:36 +0100
> 
> When restoring a desktop session where a buffer has
> highlight-changes-mode enabled, if Emacs is starting in daemon mode, it
> locks up before opening the socket. There is no error message.
> 
> If Emacs is not starting in daemon mode, or if the desktop session file
> does not list highlight-changes-mode, everything is fine.
> 
> I have observed this problem both with Emacs 27.1 on macOS and with
> Emacs 26.3 on Ubuntu 20.04. Below I give the server an explicit name for
> convenience but this is optional to reproduce the bug.
> 
> Here is a precise recipe to reproduce. (Lines beginning with a letter
> are shell commands; lines beginning with `|` are terminal output.)

Thanks.

Since you already have a working setup for reproducing the problem,
could you please attach GDB to the daemon when it hangs, and show
both a C-level and a Lisp-level backtrace?  (This could be tricky if
you don't have a working GDB installed on your macOS system, because
LLDB isn't supported by src/.gdbinit init file.  But maybe you could
do this on Ubuntu?)  This could go a long way towards identifying the
problematic piece of code.





  reply	other threads:[~2021-03-23 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  0:30 bug#47334: 27.1; Incompatibility between daemon, desktop and highlight-changes-mode Gilles
2021-03-23 10:06 ` Eli Zaretskii [this message]
2021-03-28  1:06   ` Gilles
2021-03-28  6:36     ` Eli Zaretskii
2021-03-28 14:25       ` Gilles
2021-03-28 14:58         ` 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=83h7l289q4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=47334@debbugs.gnu.org \
    --cc=gilles.usenet@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).