From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Michael Schierl" <schierlm@gmx.de>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Crash when having malformed PBM image on screen and viewing *Messages* buffer (on Windows)
Date: Sat, 16 Jun 2007 02:20:10 +0200 [thread overview]
Message-ID: <f7ccd24b0706151720j2d50d4ddi261164c491f54939@mail.gmail.com> (raw)
In-Reply-To: <467300B7.9080501@gmx.de>
On 6/15/07, Michael Schierl <schierlm@gmx.de> wrote:
> Sorry, this should have been xpm (and not xbm and not pbm in the
> subject). And also in the bug report below it should be :type xpm,
> although it crashes with :type pbm as well.
It's perfectly reproducible, yes.
It is aborting in temp_set_point_both, in the "charpos > BUF_ZV
(buffer)" comparison. In test runs, I get charpos == 316, BUF_ZV
(buffer) = 293.
Time for someone versed in redisplay.
#0 0x7c911231 in _end__ ()
#1 0x01135627 in w32_abort () at w32fns.c:9087
#2 0x01119ed7 in temp_set_point_both (buffer=0x16c1200, charpos=350,
bytepos=350) at intervals.c:1954
#3 0x0102a503 in redisplay_window (window=24978436, just_this_one_p=0)
at xdisp.c:13523
#4 0x0102c924 in redisplay_window_0 (window=24978436) at xdisp.c:11790
#5 0x0100a0b4 in internal_condition_case_1 (
bfun=0x102c8fa <redisplay_window_0>, arg=24978436, handlers=23807125,
hfun=0x101f526 <redisplay_window_error>) at eval.c:1529
#6 0x0101f308 in redisplay_windows (window=2089944429) at xdisp.c:11769
#7 0x0101f2c9 in redisplay_windows (window=2089944429) at xdisp.c:11763
#8 0x0102e417 in redisplay_internal (preserve_echo_area=6) at xdisp.c:11329
#9 0x010596b9 in read_char (commandflag=1, nmaps=3, maps=0x82fb40,
prev_event=23824385, used_mouse_menu=0x82fb88, end_time=0x0)
at keyboard.c:2670
#10 0x0105ae41 in read_key_sequence (keybuf=0x82fcb0, bufsize=30,
prompt=23824385, dont_downcase_last=0, can_return_switch_frame=1,
fix_current_buffer=1) at keyboard.c:9218
#11 0x0105c617 in command_loop_1 () at keyboard.c:1618
#12 0x0100a347 in internal_condition_case (bfun=0x105c486 <command_loop_1>,
handlers=23892617, hfun=0x105645e <cmd_error>) at eval.c:1481
#13 0x01050656 in command_loop_2 () at keyboard.c:1329
#14 0x0100a27c in internal_catch (tag=23882753,
func=0x1050633 <command_loop_2>, arg=23824385) at eval.c:1222
#15 0x010504a3 in command_loop () at keyboard.c:1308
#16 0x01050537 in recursive_edit_1 () at keyboard.c:1006
#17 0x0105061c in Frecursive_edit () at keyboard.c:1067
#18 0x01002a2b in main (argc=2, argv=0xf826a8) at emacs.c:1768
#19 0x01001247 in __mingw_CRTStartup ()
#20 0x01001298 in mainCRTStartup ()
#21 0x7c816fd7 in _end__ ()
Juanma
next prev parent reply other threads:[~2007-06-16 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 21:04 Crash when having malformed PBM image on screen and viewing *Messages* buffer (on Windows) Michael Schierl
2007-06-15 21:12 ` Michael Schierl
2007-06-16 0:20 ` Juanma Barranquero [this message]
2007-06-17 21:14 ` Jason Rumney
2007-06-17 21:25 ` Juanma Barranquero
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=f7ccd24b0706151720j2d50d4ddi261164c491f54939@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=schierlm@gmx.de \
/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).