all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Matthew Leach <matthew@mattleach.net>
Cc: 23259@debbugs.gnu.org
Subject: bug#23259: 25.1.50; Xerror: "BadLength" on extreme zoom causing emacs to segfault
Date: Sun, 10 Apr 2016 18:01:56 +0300	[thread overview]
Message-ID: <83vb3ph5i3.fsf@gnu.org> (raw)
In-Reply-To: <87zit120yf.fsf@mattleach.net> (message from Matthew Leach on Sun, 10 Apr 2016 11:49:12 +0100)

> From: Matthew Leach <matthew@mattleach.net>
> Date: Sun, 10 Apr 2016 11:49:12 +0100
> 
> emacs -Q
> open a file, emacs/src/process.c, say.
> C-x C-=
> and keep pressing
> C-=
> 
> Emacs will grind to a halt a little but will eventually segfault when
> the zoom is extreme enough.
> 
> Attached is the backtrace.  It looks as though X has thrown an error,
> maybe we need to limit the amount of zoom that Emacs allows?

Probably.  However, the interesting question is: what values to use as
limits?

Also, this backtrace is not useful, since the X errors are by default
asynchronous.  Could you please run Emacs in synchronous X mode (see
etc/DEBUG for how), and present the backtrace then?  Also, please
tell:

  . what is the maximum value of the scale factor you see on the mode
    line before Emacs crashes

  . what is the value returned by display-pixel-width

  . what is the values returned by frame-char-width and
    frame-char-height

I'll try to prepare a patch using the above data.

Thanks.





  reply	other threads:[~2016-04-10 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10 10:49 bug#23259: 25.1.50; Xerror: "BadLength" on extreme zoom causing emacs to segfault Matthew Leach
2016-04-10 15:01 ` Eli Zaretskii [this message]
2016-04-10 15:33   ` Matthew Leach
2016-04-10 16:24     ` Eli Zaretskii
2016-04-10 16:36       ` Matthew Leach
2016-04-10 16:52         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83vb3ph5i3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23259@debbugs.gnu.org \
    --cc=matthew@mattleach.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.