[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#22739: 25.0.50; Hangs on revertig buffer

From: Óscar Fuentes
Subject: bug#22739: 25.0.50; Hangs on revertig buffer
Date: Fri, 19 Feb 2016 23:09:02 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

> This seems to say that the display engine signaled an error.  If so,
> the error message should be in *Messages*.  One way of accessing the
> error messages is to use the facilities in etc/emacs-buffer.gdb (after
> you instruct GDB to load that file with the "source" command) to
> access the text of *Messages*.

After using ybuffer-save for recovering *Messages*, the last lines are


The "reverting... reverted" lines are the output of a wrapper function I
wrote for executing revert-buffer:

(defun ofv-revert-buffer ()
  (message "reverting...")
  (revert-buffer nil (not (buffer-modified-p)))
  (message "reverted"))

It is interesting that the last line of *Messages* is "Quit", but the
minibuffer on the frozen Emacs session shows "reverted". From where
comes "Quit"? Why it was not displayed? When Emacs froze, I tried C-g,
but that was after a few seconds.

> An alternative is to put a breakpoint
> in Fsignal, and look at the error symbol and data when the breakpoint
> breaks, using the commands in src/.gdbinit that display Lisp objects.
> (But do NOT use "pp", because it invokes a function inside Emacs.)

I'm afraid that the Emacs instance is not resumable anymore. After using
the "finish" trick on the previous message, I was unable to interrup
Emacs either with C-c on the gdb console (as I did the first time after
attaching gdb) nor C-z on the Emacs window (as DEBUG suggests.) I sent a
SIGSTOP signal to the Emacs process to gain access to the gdb command
line and now it can't resume.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]