unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: Jason Rumney <jasonr@gnu.org>, emacs-devel@gnu.org
Subject: Re: [lekktu@gmail.com: Re: Crash when having malformed PBM image on screen and viewing *Messages* buffer (on Windows)]
Date: Mon, 06 Aug 2007 13:23:14 -0400	[thread overview]
Message-ID: <87zm14efwd.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1IDnDH-0003kg-UB@fencepost.gnu.org> (Richard Stallman's message of "Wed\, 25 Jul 2007 16\:12\:03 -0400")

> As I said in the original thread about this bug, the problem can be
> reproduced on GNU/Linux.  The recipe to reproduce it is:
>
> 	- start emacs -Q
> 	- run this in *scratch* buffer
>
> 	(progn
> 	  (put-image '(image :type pbm :data "") 0)
> 	  (pop-to-buffer "*Messages*")
> 	  (goto-char (point-max)))
>
> 	Now press <down> <right> <down> <right>.

The problem is that the size of the *Messages* buffer shrinks during
redisplay_window, as a result of message log truncation: from

...
unsigned char *) 0x85da2f8 "pe pbm :data )'
call-interactively: End of bufferNot a PBM image: `(image :type pbm :data )'
call-interactively: End of buffer

to

...
unsigned char *) 0x85da4cc "pe pbm :data )'
call-interactively: End of bufferNot a PBM image: `(image :type pbm :data )' [2 times]

I've checked in code into both the trunk and branch to handle this
corner case.

  reply	other threads:[~2007-08-06 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 18:06 [lekktu@gmail.com: Re: Crash when having malformed PBM image on screen and viewing *Messages* buffer (on Windows)] Richard Stallman
2007-07-25 10:57 ` Jason Rumney
2007-07-25 20:12   ` Richard Stallman
2007-08-06 17:23     ` Chong Yidong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-17 21:49 Richard Stallman

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=87zm14efwd.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=rms@gnu.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).