unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: joakim@verona.se
Cc: 8472@debbugs.gnu.org
Subject: bug#8472: 24.0.50;  weird emacs bugs causing data lossage
Date: Mon, 11 Apr 2011 05:36:06 -0400	[thread overview]
Message-ID: <E1Q9DXS-00087S-Qb@fencepost.gnu.org> (raw)
In-Reply-To: <m3ei59dtrw.fsf@verona.se> (joakim@verona.se)

> From: joakim@verona.se
> Cc: 8472@debbugs.gnu.org
> Date: Mon, 11 Apr 2011 11:25:23 +0200
> 
> I got it working by suspending gdb and resuming it again. and sending
> signals to Emacs (I was a bit furious so this part is a bit hazy)

So from that point on, please use the procedure in etc/DEBUG to find
out where it is looping.

> Ok. So the hang happens somewhere else. The symptom is that nothing
> happens on the display but emacsclient can communicate.

Do you remember what was displayed in the minibuffer at that point, by
any chance?  Was it a single screen line or more than that?  Or maybe
only part of the text was visible, i.e. Emacs froze when it tried to
enlarge (a.k.a. "resize") the echo area?

> Also, whenever I manage to break into the process with gdb the backtrace
> shows Emacs is in the select call. With strace I see that Emacs is not
> stuck there but loops.

This is normal, or at least it could be normal: Emacs usually checks
for any arriving input from any possible sources, and that includes
calls to `select'.  Seeing a lot of calls to `select' is not in itself
a sign of an infloop.  Only the procedure in etc/DEBUG (or something
similar) can give a definitive answer to that.

> So I figure theres some poll loop running closely around the select.

Emacs does that all the time, that's how it knows that input arrived
from a subprocess or a socket, for example.  It polls.

> >> - the file was truncated. Maybe this is due to a combination of
> >>   narrowing and automatic save.
> >
> > Can't happen, auto-save forces temporary widening of the buffer (as
> > you'd expect ;-).
> 
> Well. The funny thing is that the truncated content of the file is the
> exact same content I see in the narrowed buffer on screen.
> 
> Org narrows in another window and buffer somehow. Could that interfere?
> I dont know the term for what it does yet. "indirect buffer" maybe?

Could be.  IOW, if auto-save happened in a buffer whose contents was
just the text you found in the auto-save file.





      reply	other threads:[~2011-04-11  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10 19:39 bug#8472: 24.0.50; weird emacs bugs causing data lossage joakim
2011-04-11  7:56 ` Eli Zaretskii
2011-04-11  9:25   ` joakim
2011-04-11  9:36     ` Eli Zaretskii [this message]

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=E1Q9DXS-00087S-Qb@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=8472@debbugs.gnu.org \
    --cc=joakim@verona.se \
    /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).