unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yagnesh Raghava Yakkala <hi@yagnesh.org>,
	Paul Eggert <eggert@cs.ucla.edu>
Cc: 16033@debbugs.gnu.org
Subject: bug#16033: 24.3.50; window--reseize-this-window, args-out-of-range
Date: Tue, 03 Dec 2013 09:34:34 +0200	[thread overview]
Message-ID: <83vbz64cc5.fsf@gnu.org> (raw)
In-Reply-To: <877gbmxxec.fsf@yagnesh.org>

> From: Yagnesh Raghava Yakkala <hi@yagnesh.org>
> Date: Tue, 03 Dec 2013 15:26:51 +0900
> 
> 
> Latest build from emacs
> trunk(yamaoka@jpl.org-20131203045417-2co55ww8uqmoh5cb) I get the
> following backtrace.
> 
> --8<---------------cut here---------------start------------->8---
> Debugger entered--Lisp error: (args-out-of-range -19 0 2147483001)
>   set-window-new-pixel(#<window 3 on *scratch*> -19 t)
>   window--resize-this-window(#<window 3 on *scratch*> -19 nil nil t before 646)

Paul, it's because of your commit:

  revno: 115359
  committer: Paul Eggert <eggert@cs.ucla.edu>
  branch nick: trunk
  timestamp: Tue 2013-12-03 02:27:10 +0000
  message:
    Minor integer overflow fixes.

    * window.c (Fset_window_new_pixel, grow_mini_window):
    * xdisp.c (Fwindow_text_pixel_size):
    Avoid undefined behavior on signed integer overflow.
    * xfns.c (x_set_mouse_color):
    Check that drag shape fits in 'unsigned', since that's what X wants.

The modified test at the beginning of Fset_window_new_pixel doesn't
DTRT when SIZE is negative (which it legitimately can be when ADD is
non-nil).





  reply	other threads:[~2013-12-03  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  6:26 bug#16033: 24.3.50; window--reseize-this-window, args-out-of-range Yagnesh Raghava Yakkala
2013-12-03  7:34 ` Eli Zaretskii [this message]
2013-12-03  7:56   ` martin rudalics
2013-12-03  7:59     ` Yagnesh Raghava Yakkala
2013-12-03  8:15       ` martin rudalics
2013-12-03 21:39     ` Paul Eggert
2013-12-04 10:49       ` martin rudalics

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=83vbz64cc5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=16033@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=hi@yagnesh.org \
    /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).