unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 22739@debbugs.gnu.org
Subject: bug#22739: 25.0.50; Hangs on revertig buffer
Date: Sat, 20 Feb 2016 10:08:08 +0200	[thread overview]
Message-ID: <834md3rehj.fsf@gnu.org> (raw)
In-Reply-To: <874md4cpz5.fsf@wanadoo.es> (message from Óscar Fuentes on Fri, 19 Feb 2016 23:09:02 +0100)

> From: Óscar Fuentes <ofv@wanadoo.es>
> Cc: 22739@debbugs.gnu.org
> Date: Fri, 19 Feb 2016 23:09:02 +0100
> 
> Eli Zaretskii <eliz@gnu.org> 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
> 
> reverting...
> reverted
> Quit
> 
> The "reverting... reverted" lines are the output of a wrapper function I
> wrote for executing revert-buffer:
> 
> (defun ofv-revert-buffer ()
>   (interactive)
>   (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.

It was probably not displayed because Emacs was busy doing something,
so it didn't enter redisplay.

In any case, that C-g is most probably the reason for what you saw
using "finish" -- it caused Emacs to throw to top level.

IOW, the data you collected is probably not relevant to the root cause
of the problem.

> 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)

Are you saying that just attaching GDB didn't stop Emacs, and you
needed C-c to do that?

> 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.

What do you mean by "cannot resume"?  What happens if you try?
What happens if you kill the GDB process, and then attach another GDB
to Emacs?

Thanks.





  reply	other threads:[~2016-02-20  8:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19  3:33 bug#22739: 25.0.50; Hangs on revertig buffer Óscar Fuentes
2016-02-19  8:16 ` Eli Zaretskii
2016-02-19 12:44   ` Óscar Fuentes
2016-02-19 15:28     ` Eli Zaretskii
2016-03-06  1:28     ` Óscar Fuentes
2016-03-06  3:41       ` Eli Zaretskii
2016-03-06  4:39         ` Óscar Fuentes
2016-03-06 16:22           ` Eli Zaretskii
2016-03-07  0:29             ` Óscar Fuentes
2016-03-07 16:32               ` Eli Zaretskii
2016-02-19 13:04   ` Óscar Fuentes
2016-02-19 13:21   ` Óscar Fuentes
2016-02-19 15:45     ` Eli Zaretskii
2016-02-19 22:09       ` Óscar Fuentes
2016-02-20  8:08         ` Eli Zaretskii [this message]
2016-02-20 16:40           ` Óscar Fuentes

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=834md3rehj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22739@debbugs.gnu.org \
    --cc=ofv@wanadoo.es \
    /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).