unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "T.V Raman" <tv.raman.tv@gmail.com>
Cc: 16711@debbugs.gnu.org
Subject: bug#16711: 24.3.50; Error: pre-redisplay-function
Date: Sat, 26 Dec 2015 22:14:23 -0500	[thread overview]
Message-ID: <jwva8owk2pu.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <p917g92diuc.fsf@lapdog.roam.corp.google.com> (T. V. Raman's message of "Mon, 10 Feb 2014 08:37:47 -0800")

> I've been bitten by this intermitently for the last few weeks; it
> appears to be happening more often now.
> Observed initially in W3 when rendering heavy-weight web pages; it also
> shows up in eww.

That's a problem that needs fixing.

> You get a variable depth exeeds max eval depth error repeatedly --
> turning on debug doesn't yield any additional info.

That's not very surprising: since pre-redisplay-function is run during
redisplay, running redisplay (e.g. to show a backtrace) from within it
would require extra care to try and avoid inf-looping.

Maybe we should re-introduce stack-trace-on-error, or something
equivalent, for those cases.

In the mean time, can you run Emacs within GDB and set a breakpoint on
maybe_call_debugger?


        Stefan





      parent reply	other threads:[~2015-12-27  3:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 16:37 bug#16711: 24.3.50; Error: pre-redisplay-function T.V Raman
2014-02-12  2:46 ` Stefan Monnier
2014-02-13  2:35   ` T. V. Raman
2015-12-26 13:32     ` Lars Ingebrigtsen
2015-12-26 19:56       ` T. V. Raman
2015-12-26 20:00         ` Lars Ingebrigtsen
2015-12-27  0:51           ` T. V. Raman
2015-12-27  6:11             ` Lars Ingebrigtsen
2015-12-27 15:41               ` T. V. Raman
2020-11-18 15:24                 ` Stefan Kangas
2020-11-18 16:59                 ` Stefan Monnier
2015-12-27  3:14 ` Stefan Monnier [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=jwva8owk2pu.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=16711@debbugs.gnu.org \
    --cc=tv.raman.tv@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).