unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: John Mastro <john.b.mastro@gmail.com>
Cc: djcb@djcbsoftware.nl, Christophe.Troestler@umons.ac.be,
	24109@debbugs.gnu.org
Subject: bug#24109: 24.5; Long lines in message mode make Emacs irresponsive
Date: Sat, 30 Jul 2016 21:48:55 +0300	[thread overview]
Message-ID: <83fuqrotbc.fsf@gnu.org> (raw)
In-Reply-To: <CAOj2CQT88wxE1xN6smjSSsBt2eb4NjMhiVKbgJ3MiXtrron4-Q@mail.gmail.com> (message from John Mastro on Sat, 30 Jul 2016 11:30:12 -0700)

> From: John Mastro <john.b.mastro@gmail.com>
> Date: Sat, 30 Jul 2016 11:30:12 -0700
> Cc: martin rudalics <rudalics@gmx.at>, 24109@debbugs.gnu.org, djcb@djcbsoftware.nl, 
> 	Christophe.Troestler@umons.ac.be
> 
> Eli Zaretskii <eliz@gnu.org> wrote:
> > Btw, line 1452 in fns.c is not in assq_no_quit, not in any Emacs 24.x
> > version (the bug is reported for 24.5).  In 25.1, line 1452 is indeed
> > inside assq_no_quit, so perhaps the version and/or line numbers are
> > reported incorrectly.
> 
> The apparent discrepancy is because the reporter is using 24.5 and
> reported the bug against that version, but the author/maintainer of mu4e
> reproduced the bug in 25.1 and posted the backtrace.

Thanks.

Assuming this problem can be reproduced at will by the reporters, the
best way forward is to use the technique described in etc/DEBUG for
finding the infinite loop, in the section named "If the symptom of the
bug is that Emacs fails to respond".  But before someone does that, I
suggest to rebuild Emacs without optimizations, as those can easily
lead the investigation astray.





  reply	other threads:[~2016-07-30 18:48 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 11:36 bug#24109: 24.5; Long lines in message mode make Emacs irresponsive Christophe Troestler
2016-07-30  7:07 ` Eli Zaretskii
2016-07-30 12:38   ` Christophe Troestler
2016-07-30 14:52     ` Clément Pit--Claudel
2016-07-30 15:55     ` Eli Zaretskii
2016-07-30 17:01       ` martin rudalics
2016-07-30 17:13         ` Eli Zaretskii
2016-07-30 17:30           ` martin rudalics
2016-07-30 18:02             ` Eli Zaretskii
2016-07-30 18:30               ` John Mastro
2016-07-30 18:48                 ` Eli Zaretskii [this message]
2016-07-30 19:22                 ` Dirk-Jan C. Binnema
2016-08-30 12:38 ` Yuri D'Elia
2016-08-30 12:45   ` Yuri D'Elia
2016-08-30 15:29   ` Eli Zaretskii
2016-08-30 15:51     ` Yuri D'Elia
2016-08-30 16:25       ` Eli Zaretskii
2016-08-31  9:15         ` Yuri D'Elia
2016-08-31 14:37           ` Eli Zaretskii
2016-08-31 15:51             ` Yuri D'Elia
2016-08-31 16:12               ` Eli Zaretskii
2016-08-31 16:49                 ` Yuri D'Elia
2016-09-01  2:35                   ` Eli Zaretskii
2016-09-01 14:30                     ` Eli Zaretskii
2016-09-01 14:39                       ` Yuri D'Elia
2016-09-01 14:48                         ` Yuri D'Elia
2016-09-01 15:18                           ` Eli Zaretskii
2016-09-01 15:37                             ` Yuri D'Elia
2016-09-01 16:00                               ` Eli Zaretskii
2016-09-03 13:25                                 ` Eli Zaretskii
     [not found]                       ` <28e7ddc58bcfeec0@fake-msgid>
2016-10-01 17:10                         ` Yuri D'Elia
2016-10-01 17:47                           ` Eli Zaretskii
2016-10-01 18:25                           ` Yuri D'Elia
2016-10-02  7:09                             ` Eli Zaretskii
2016-10-04  7:16                               ` Yuri D'Elia
2016-10-04  7:56                                 ` Eli Zaretskii
2016-10-08  7:55                               ` Eli Zaretskii
2016-10-08 15:27                                 ` Yuri D'Elia
2016-10-08 15:38                                   ` Eli Zaretskii
2016-10-08 15:42                                     ` Yuri D'Elia
2016-10-09 19:21                                   ` Christophe Troestler
2016-10-10  6:08                                     ` 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=83fuqrotbc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24109@debbugs.gnu.org \
    --cc=Christophe.Troestler@umons.ac.be \
    --cc=djcb@djcbsoftware.nl \
    --cc=john.b.mastro@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).