From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: vc-annotate causes Emacs to die
Date: Tue, 23 Jul 2002 13:29:47 +0000 (UTC) [thread overview]
Message-ID: <m17WzjX-000IeMC@localhost> (raw)
In today's CVS snapshot, Tue, 2002 Jul 23 13:05 UTC,
GNU Emacs 21.3.50.123 (i686-pc-linux-gnu, X toolkit).
Emacs started with:
emacs -q --no-site-file --eval '(blink-cursor-mode 0)'
`C-x v g' (vc-annotate) causes Emacs to die.
To reproduce, visit:
emacs/lisp/etc/NEWS
or
emacs/lisp/calendar/solar.el
and give the vc-annotate command `C-x v g'
The backtrace is:
#0 0x080aad1e in x_fill_glyph_string (s=0xbfffe874, face_id=12, start=35,
end=80, overlaps_p=0) at xterm.c:1420
#1 0x080ab615 in x_draw_glyphs (w=0x82d53e8, x=305, row=0x84f7b9c,
area=TEXT_AREA, start=0, end=80, hl=DRAW_NORMAL_TEXT, overlaps_p=0)
at xterm.c:5142
#2 0x080adee6 in x_write_glyphs (start=0x8528a98, len=80) at xterm.c:5339
#3 0x08053c4c in update_text_area (w=0x82d53e8, vpos=3) at dispnew.c:4265
#4 0x08054082 in update_window_line (w=0x82d53e8, vpos=3,
mouse_face_overwritten_p=0xbfffec68) at dispnew.c:4489
#5 0x080539eb in update_window (w=0x82d53e8, force_p=0) at dispnew.c:4145
#6 0x0805347b in update_window_tree (w=0x84bb258, force_p=0) at dispnew.c:3879
#7 0x08053466 in update_window_tree (w=0x84c4420, force_p=0) at dispnew.c:3877
#8 0x08053385 in update_frame (f=0x84484b0, force_p=0, inhibit_hairy_id_p=0)
at dispnew.c:3816
#9 0x08067224 in redisplay_internal (preserve_echo_area=0) at xdisp.c:8964
#10 0x0806617c in redisplay () at xdisp.c:8374
#11 0x080d6075 in read_char (commandflag=1, nmaps=2, maps=0xbffff424,
prev_event=405373956, used_mouse_menu=0xbffff470) at keyboard.c:2323
#12 0x080dccb0 in read_key_sequence (keybuf=0xbffff574, bufsize=30,
prompt=405373956, dont_downcase_last=0, can_return_switch_frame=1,
fix_current_buffer=1) at keyboard.c:8363
#13 0x080d4be8 in command_loop_1 () at keyboard.c:1470
#14 0x08128159 in internal_condition_case (bfun=0x80d48e0
<command_loop_1>
handlers=405470516, hfun=0x80d44f4 <cmd_error>) at eval.c:1349
#15 0x080d47b8 in command_loop_2 () at keyboard.c:1271
#16 0x08127ced in internal_catch (tag=405431844,
func=0x80d4794 <command_loop_2>, arg=405373956) at eval.c:1109
#17 0x080d4763 in command_loop () at keyboard.c:1250
#18 0x080d42b0 in recursive_edit_1 () at keyboard.c:966
#19 0x080d43e0 in Frecursive_edit () at keyboard.c:1022
#20 0x080d32b3 in main (argc=5, argv=0xbffffb34, envp=0xbffffb4c)
at emacs.c:1625
--
Robert J. Chassell bob@rattlesnake.com
Rattlesnake Enterprises http://www.rattlesnake.com
next reply other threads:[~2002-07-23 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 13:29 Robert J. Chassell [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-26 0:36 [spiegel@gnu.org: Re: [Fwd: vc-annotate causes Emacs to die]] Richard Stallman
2002-08-26 13:33 ` Gerd Moellmann
2002-08-26 18:26 ` vc-annotate causes Emacs to die Andre Spiegel
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=m17WzjX-000IeMC@localhost \
--to=bob@rattlesnake.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).