Mule redisplay crash
23 years, 4 months
Gunnar Evermann
Gunnar Evermann
This is one of the oldest crashes on my to do list.
loading the following in a vanilla Mule XEmacs will trigger a crash.
(defun delete-and-split ()
(interactive)
(delete-other-windows)
(split-window))
(split-window-vertically)
(insert "$B$,(B")
(backward-char)
(redraw-frame)
(delete-and-split)
Fatal error: assertion failed, file /deb-huge/home/gunnar/src/XEmacs/xemacs/src/objects.h, line 143, RECORD_TYPEP (obj, &lrecord_font_instance)
#3 0x808eb81 in assert_failed (file=0x8218c60 "/deb-huge/home/gunnar/src/XEmacs/xemacs/src/objects.h", line=143,
expr=0x8218d40 "RECORD_TYPEP (obj, &lrecord_font_instance)")
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/emacs.c:2825
#4 0x80c9db4 in error_check_font_instance (obj=136776524)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/objects.h:143
#5 0x81c730f in x_output_string (w=0x85a8c10, dl=0x8609808, buf=0x85e7640, xpos=4, xoffset=0, clip_start=4,
width=16, findex=0, cursor=1, cursor_start=4, cursor_width=16, cursor_height=13)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/redisplay-x.c:883
#6 0x81c60d5 in x_output_display_block (w=0x85a8c10, dl=0x8609808, block=0, start=0, end=1, start_pixpos=4,
cursor_start=4, cursor_width=16, cursor_height=13)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/redisplay-x.c:390
#7 0x81799c2 in redisplay_output_display_block (w=0x85a8c10, dl=0x8609808, block=0, start=0, end=1,
start_pixpos=4, cursor_start=4, cursor_width=16, cursor_height=13)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/redisplay-output.c:1088
#8 0x8178a28 in output_display_line (w=0x85a8c10, cdla=0x0, ddla=0x85e2668, line=1, force_start=4, force_end=20)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/redisplay-output.c:751
#9 0x8179839 in redraw_cursor_in_window (w=0x85a8c10, run_end_begin_meths=1)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/redisplay-output.c:1029
#10 0x81798be in redisplay_redraw_cursor (f=0x8577f00, run_end_begin_meths=1)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/redisplay-output.c:1054
#11 0x81760e9 in Fforce_cursor_redisplay (frame=139951872)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/redisplay.c:8938
#12 0x8176761 in text_cursor_visible_p_changed (specifier=137474936, w=0x85e8148, oldval=136988916)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/redisplay.c:9005
#13 0x81999b1 in recompute_one_cached_specifier_in_window (specifier=137474936, w=0x85e8148)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/specifier.c:2812
#14 0x8199b67 in recompute_all_cached_specifiers_in_window (w=0x85e8148)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/specifier.c:2854
#15 0x81d5e1e in Fset_window_buffer (window=140411208, buffer=137541312)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/window.c:3198
#16 0x81d6b4e in Fsplit_window (window=140151824, chsize=136988916, horflag=136988916)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/window.c:3503
#17 0x8094ed9 in Feval (form=140010872) at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/eval.c:2975
#18 0x8090870 in Fprogn (args=140010812) at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/eval.c:767
#19 0x8096629 in funcall_lambda (fun=140010896, nargs=0, args=0xbffff048)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/eval.c:3497
#20 0x8095522 in Feval (form=140007804) at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/eval.c:3081
#21 0x8146b51 in readevalloop (readcharfun=140386240, sourcename=139813548, evalfun=0x80947b0 <Feval>, printflag=0)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/lread.c:1448
[...]
#43 0x808d520 in xemacs_21_2_b23_i586_pc_linux (argc=4, argv=0xbffffc34, envp=0xbffffc48, restart=0)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/emacs.c:1898
#44 0x808e0ab in main (argc=4, argv=0xbffffc34, envp=0xbffffc48)
at /deb-huge/home/gunnar/src/XEmacs/xemacs/src/emacs.c:2323
The problem is that the face cache doesn't contain the font instance
for the relevant charset or to be precise that the cache has been
cleared but we do not regenerate the necessary entries.
A quick fix for the crash would be adding a call to
ensure_face_cachel_contains_charset() at the relevant place in
x_output_string like this:
Index: redisplay-x.c
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/src/redisplay-x.c,v
retrieving revision 1.23.2.17
diff -u -r1.23.2.17 redisplay-x.c
--- redisplay-x.c 1999/10/15 10:11:51 1.23.2.17
+++ redisplay-x.c 1999/12/13 22:58:35
＠＠ -879,10 +879,14 ＠＠
for (i = 0; i < nruns; i++)
{
- Lisp_Object font = FACE_CACHEL_FONT (cachel, runs[i].charset);
- struct Lisp_Font_Instance *fi = XFONT_INSTANCE (font);
+ Lisp_Object font;
+ struct Lisp_Font_Instance *fi;
int this_width;
int need_clipping;
+
+ ensure_face_cachel_contains_charset(cachel, window, runs[i].charset);
+ font = FACE_CACHEL_FONT (cachel, runs[i].charset);
+ fi = XFONT_INSTANCE (font);
if (EQ (font, Vthe_null_font_instance))
continue;
This works but is kindof expensive to do, as x_output_string is called
very very often :-)
Maybe our Mule and redisplay experts can try to come up with something
more clever...
Gunnar
- 3 participants
- 2 comments
Small windows with scroll-step set
23 years, 5 months
Mike Alexander
Mike Alexander
The problem described in
<http://www.xemacs.org/list-archives/xemacs-beta/200003/msg00645.html>
is still occurring for me sometimes. This causes random crashes if
you have a value set for scroll-step. One way that I've made it
happen, although not every time, is to run XEmacs -vanilla,
immediately use M-: (i.e., don't type into the *scratch* buffer) to
set toolbar-visible-p and gutter-buffers-tab-visible-p to nil and
scroll-step to 15, then do a File->Save As. This doesn't make much
sense to do since it tries to save the default *scratch* buffer, but
it sometimes causes the crash.
The patch below avoids this problem. It occurs if the height of a
window is so small that not even one line can be formatted in it. In
this case the line cache will always be empty and
point-in-line-start-cache will return -1 which was causing vmotion-1
to assert. I looked at the various callers of vmotion-1 and it
appears that it is reasonable to just have it return the input point
unchanged in this case, so that's what I did. If this is not the
right thing to do, I'd be happy to hear alternative suggestions.
Mike
2000-04-29 Mike Alexander <mta(a)arbortext.com>
* indent.c (vmotion_1): If point_in_line_start_cache fails simply
return the input position instead of asserting out.
Index: src/indent.c
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/src/indent.c,v
retrieving revision 1.9.2.4
diff -u -r1.9.2.4 indent.c
--- indent.c 2000/02/07 07:59:19 1.9.2.4
+++ indent.c 2000/04/29 06:58:00
＠＠ -624,8 +624,15 ＠＠
/* #### This assertion must be true before the if statements are hit
but may possibly be wrong after the call to
point_in_line_start_cache if orig is outside of the visible
- region of the buffer. Handle this. */
- assert (elt >= 0);
+ region of the buffer. Handle this.
+
+ This occurs sometimes if scroll-step is non-zero and the window
+ is very small. In this case it's not possible to lay out any lines
+ in the window and point_in_line_start_cache returns -1 because
+ the line cache is empty. In this case we will just return the
+ original point and hope for the best. */
+ if (elt < 0)
+ return orig;
/* Moving downward. */
if (vtarget > 0)
- 2 participants
- 2 comments
vm crashes on linux console
23 years, 5 months
Giacomo Boffi
Giacomo Boffi
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
In XEmacs 21.2 (beta34) "Molpe" [Lucid] (i586-pc-linux) of Tue Jul 18 2000 on boffi95
configured using `configure --extra-verbose --without-wmcommand --with-athena=3d --with-modules --debug --error-checking=none --use-union-type --with-clash-detection --rel-alloc'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
i started xemacs on linux console, then i started vm (M-x vm RET),
bang
Recent keystrokes:
inappropriate
Lisp backtrace follows:
# (unwind-protect ...)
# (unwind-protect ...)
# (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque-ptr, adr=0x81e9df8) 0x823bd68> ...)
# (unwind-protect ...)
# bind (inhibit-quit frame-being-created)
make-frame(nil)
# bind (params types)
vm-goto-new-frame(primary-folder folder)
apply(vm-goto-new-frame (primary-folder folder))
# bind (w types)
vm-goto-new-folder-frame-maybe(primary-folder folder)
apply(vm-goto-new-folder-frame-maybe (primary-folder folder))
# bind (full-startup did-read-index-file folder-buffer first-time totals-blurb preserve-auto-save-file)
byte-code("..." [bufferp folder nil preserve-auto-save-file totals-blurb first-time folder-buffer did-read-index-file full-startup expand-file-name vm-primary-inbox vm-folder-directory file file-directory-p error "%s is a directory" vm-get-file-buffer default-directory t no-conversion coding-system-for-read default-enable-multibyte-characters enable-local-variables inhibit-local-variables message "Reading %s..." find-file-noselect item vm-folder-history "Reading %s... done" vm-fsfemacs-mule-p enable-multibyte-characters set-buffer-multibyte buffer-file-coding-system current-load-list vm-xemacs-mule-p get-coding-system no-conversion-unix no-conversion-dos no-conversion-mac binary buffer-modified-p omodified buffer-read-only ((set-buffer-modified-p omodified)) encode-coding-region set-buffer-file-coding-system decode-coding-region coding-system-base ((set-buffer-modified-p omodified)) vm-check-for-killed-summary vm-check-for-killed-presentation 0 vm-messages-not-on-disk major-!
mode vm-mode buffer-file-name file-newer-than-file-p make-auto-save-file-name read-only default-value vm-folder-read-only buffer-disable-undo abbrev-mode auto-fill-mode vm-mode-internal vm-read-index-file-maybe vm-assimilate-new-messages vm-gobble-visible-header-variables vm-gobble-bookmark vm-gobble-pop-retrieved vm-gobble-imap-retrieved vm-gobble-summary vm-gobble-labels vm-start-itimers-if-needed this-command apply vm-goto-new-folder-frame-maybe (folder) (primary-folder folder) vm-summary-buffer vm-presentation-buffer buffer-to-display vm-display vm startup vm-raise-frame-at-startup vm-raise-frame vm-emit-totals-blurb vm-thoughtfully-select-message vm-update-summary-and-mode-line vm-toolbar-support-possible-p vm-use-toolbar "Initializing toolbar..." vm-toolbar-install-toolbar "Initializing toolbar... done" vm-toolbar-update-toolbar vm-use-menus vm-menu-support-possible-p vm-menu-install-visited-folders-menu vm-should-generate-summary vm-summarize vm-mutable-frames vm-frame-!
per-summary vm-mutable-windows switch-to-buffer vm-message-list vm-preview-current-message run-hooks vm-visit-folder-hook substitute-command-keys "Auto save file is newer; consider \\[recover-file]. FOLDER IS READ ONLY." throw done vm-auto-get-new-mail vm-block-new-mail "Checking for new mail for %s..." buffer-name vm-get-spooled-mail vm-startup-message-displayed vm-display-startup-message input-pending-p] 7)
# (catch done ...)
# bind (read-only folder)
#<compiled-function (&optional folder read-only) "...(7)" [vm-session-initialization done (byte-code "À !? À !« ªà ®É\n \" Í !«ÎÏ \"ªÇÐ !®Á «É !®ÒÂÓ ØÙ \"Ú ! ®\n ＠¬ B )ØÝ \"-)q « «àÂ!á\"B\"#«Åä!!äå!=¬»ä!!äæ!=¬±ä!!äç!=¬§ä!!äè!=¬Âé * +ìíed!#îÓÂ\"ïed!#+ «±ð!!ðÓ!=¬§ð!!ðè!=¬Âé * +ñíed!#îÓÂ\"ïed!#+ò ó é ¬ô56÷=?8é ?ùú 8\"®;®üý!®
+=
«þp!ÿô!＠
- 2 participants
- 1 comments
Re: Small windows with scroll-step set
23 years, 6 months
Jan Vroonhof
Jan Vroonhof
Mike Alexander <mta(a)arbortext.com> writes:
> I did that. It doesn't lay out any lines because the height of the
> window is less than the height of one line. I don't know enough
> about the redisplay code to know if this is supposed to be impossible
> or if it is normal but the redisplay code isn't handling it right.
Could you try whether this (untested) attempt at fixing
update_line_start_cache helps?
Index: redisplay.c
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs-20/src/redisplay.c,v
retrieving revision 1.55.2.56
diff -u -r1.55.2.56 redisplay.c
--- redisplay.c 2000/05/09 11:54:57 1.55.2.56
+++ redisplay.c 2000/05/11 18:15:14
＠＠ -87,16 +87,10 ＠＠
#define LEFT_GLYPHS 2
#define RIGHT_GLYPHS 3
-/* Set the vertical clip to 0 if we are currently updating the line
- start cache. Otherwise for buffers of line height 1 it may fail to
- be able to work properly because regenerate_window will not layout
- a single line. */
#define VERTICAL_CLIP(w, display) \
- (updating_line_start_cache \
- ? 0 \
- : ((WINDOW_TTY_P (w) | (!display && scroll_on_clipped_lines)) \
+ ((WINDOW_TTY_P (w) | (!display && scroll_on_clipped_lines)) \
? INT_MAX \
- : vertical_clip))
+ : vertical_clip)
/* The following structures are completely private to redisplay.c so
we put them here instead of in a header file, for modularity. */
＠＠ -328,9 +322,6 ＠＠
/* Minimum visible pixel width of clipped glyphs at right margin. */
int horizontal_clip;
-/* Set if currently inside update_line_start_cache. */
-static int updating_line_start_cache;
-
/* Nonzero means reading single-character input with prompt
so put cursor on minibuffer after the prompt. */
int cursor_in_echo_area;
＠＠ -5098,6 +5089,7 ＠＠
int ypos = WINDOW_TEXT_TOP (w);
int yend; /* set farther down */
int yclip = WINDOW_TEXT_TOP_CLIP (w);
+ int force;
prop_block_dynarr *prop;
layout_bounds bounds;
＠＠ -5151,10 +5143,14 ＠＠
else
prop = 0;
+ /* When we are computing things for scrolling purposes, make
+ sure at least one line is always generated */
+ force = (type == CMOTION_DISP);
+
/* Make sure this is set always */
/* Note the conversion at end */
w->window_end_pos[type] = start_pos;
- while (ypos < yend)
+ while (ypos < yend || force)
{
struct display_line dl;
struct display_line *dlp;
＠＠ -5207,7 +5203,7 ＠＠
the top clip and the bottom clip. */
visible_height -= (dlp->clip + dlp->top_clip);
- if (visible_height < VERTICAL_CLIP (w, 1))
+ if (visible_height < VERTICAL_CLIP (w, 1) && !force)
{
if (local)
free_display_line (dlp);
＠＠ -5251,6 +5247,8 ＠＠
generate_display_line call. */
if (start_pos > BUF_ZV (b))
break;
+
+ force = 0;
}
if (prop)
＠＠ -7834,7 +7832,6 ＠＠
validate_line_start_cache (w);
w->line_cache_validation_override++;
- updating_line_start_cache = 1;
if (from < BUF_BEGV (b))
from = BUF_BEGV (b);
＠＠ -7843,7 +7840,6 ＠＠
if (from > to)
{
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
return;
}
＠＠ -7856,7 +7852,6 ＠＠
/* Check to see if the desired range is already in the cache. */
if (from >= low_bound && to <= high_bound)
{
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
return;
}
＠＠ -7885,7 +7880,6 ＠＠
update_internal_cache_list (w, DESIRED_DISP);
if (!Dynarr_length (internal_cache))
{
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
return;
}
＠＠ -7913,7 +7907,6 ＠＠
{
Dynarr_add_many (cache, Dynarr_atp (internal_cache, 0),
Dynarr_length (internal_cache));
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
return;
}
＠＠ -7922,7 +7915,6 ＠＠
the bounds of the DESIRED structs in the first place. */
if (start >= low_bound && end <= high_bound)
{
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
return;
}
＠＠ -7945,7 +7937,6 ＠＠
Dynarr_reset (cache);
Dynarr_add_many (cache, Dynarr_atp (internal_cache, 0),
Dynarr_length (internal_cache));
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
return;
}
＠＠ -7971,7 +7962,6 ＠＠
Dynarr_reset (cache);
Dynarr_add_many (cache, Dynarr_atp (internal_cache, 0),
Dynarr_length (internal_cache));
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
return;
}
＠＠ -7980,7 +7970,6 ＠＠
Dynarr_length (internal_cache) - ic_elt);
}
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
return;
}
＠＠ -8000,23 +7989,9 ＠＠
update_internal_cache_list (w, CMOTION_DISP);
/* If this assert is triggered then regenerate_window failed
- to layout a single line. That is not supposed to be
- possible because we impose a minimum height on the buffer
- and override vertical clip when we are in here. */
- /* #### Ah, but it is because the window may temporarily
- exist but not have any lines at all if the minibuffer is
- real big. Look into that situation better. */
- if (!Dynarr_length (internal_cache))
- {
- if (old_lb == -1 && low_bound == -1)
- {
- updating_line_start_cache = 0;
- w->line_cache_validation_override--;
- return;
- }
-
- assert (Dynarr_length (internal_cache));
- }
+ to layout a single line. This is not possible since we
+ force at least a single line to be layout for CMOTION_DISP */
+ assert (Dynarr_length (internal_cache));
assert (startp == Dynarr_atp (internal_cache, 0)->start);
ic_elt = Dynarr_length (internal_cache) - 1;
＠＠ -8062,7 +8037,6 ＠＠
startp = new_startp;
if (startp > BUF_ZV (b))
{
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
return;
}
＠＠ -8096,7 +8070,6 ＠＠
while (to > high_bound);
}
- updating_line_start_cache = 0;
w->line_cache_validation_override--;
assert (to <= high_bound);
}
＠＠ -9268,15 +9241,8 ＠＠
}
void
-reinit_vars_of_redisplay (void)
-{
- updating_line_start_cache = 0;
-}
-
-void
vars_of_redisplay (void)
{
- reinit_vars_of_redisplay ();
#if 0
staticpro (&last_arrow_position);
- 3 participants
- 2 comments
assert at insdel.c:1122
23 years, 8 months
Markus Linnala
Markus Linnala
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
In XEmacs 21.2 (beta35) "Nike" [Lucid] (i686-pc-linux) of Sun Jul 23 2000 on sauna.ton.tut.fi
configured using `configure --cache-file=/dev/null --with-dialogs=athena --prefix=/opt/local'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
eval
(string-match "\\(\\.\\=\\)" ".")
This problem does not seem to be affected by OS version, also it
is present when compiled with gcc 2.95.2 and latest snapshot. I
see this also when I compile without optimisations (-O0). I
don't know which version first has the problem. But version I
currently use 21.1.4 does not die in this assert and outputs
'nil'. There does not seem to be any difference between
'-vanilla' and using my normal .emacs.
I guess this can be tested by others with following patch.
Index: tests/automated/lisp-tests.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs-20/tests/automated/Attic/lisp-tests.el,v
retrieving revision 1.1.2.12
diff -u -r1.1.2.12 lisp-tests.el
--- lisp-tests.el 2000/02/13 10:29:26 1.1.2.12
+++ lisp-tests.el 2000/07/23 18:23:40
＠＠ -831,6 +831,8 ＠＠
(Assert (equal (split-string "foo,,bar" ",+") '("foo" "bar")))
(Assert (equal (split-string ",foo,,bar," ",+") '("" "foo" "bar" "")))
+(Assert (not (string-match "\\(\\.\\=\\)" ".")))
+
;;-----------------------------------------------------
;; Test near-text buffer functions.
;;-----------------------------------------------------
Recent keystrokes:
misc-user
Recent messages (most recent first):
Loading footnote...
Loading emacsbug...done
Loading emacsbug...
Loading time...done
Loading time...
Loading /home/maage/xemacs/options.el...done
Loading font...done
Loading font...
`where-was-i-db' enabled.
Loading where-was-i-db...done
Fatal error: assertion failed, file /usr/src/xemacs/xemacs_21_2/src/insdel.c, line 1122, ( x) >= BI_BUF_BEG (buf) && x <= BI_BUF_Z (buf)
Fatal error (6).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes(a)xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type
gdb /usr/src/xemacs_21_2.build/src/xemacs core
then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)
Lisp backtrace follows:
string-match("\\(\\.\\=\\)" ".")
eval((string-match "\\(\\.\\=\\)" "."))
# bind (eval-expression-insert-value expression)
#<compiled-function (expression &optional eval-expression-insert-value) "...(18)" [eval expression values prin1 eval-expression-insert-value t] 3 767078 (list (read-from-minibuffer "Eval: " nil read-expression-map t ...) current-prefix-arg)>((string-match "\\(\\.\\=\\)" ".") nil)
call-interactively(eval-expression)
# (condition-case ... . error)
# (catch top-level ...)
zsh: 6219 abort (core dumped) ./src/xemacs
#0 0x40376d41 in __kill () from /lib/libc.so.6
(gdb) where
#0 0x40376d41 in __kill () from /lib/libc.so.6
#1 0x80b7084 in fatal_error_signal (sig=6)
at /usr/src/xemacs/xemacs_21_2/src/emacs.c:514
#2 0x40376c68 in __restore ()
at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127
#3 0x403780d8 in abort () at ../sysdeps/generic/abort.c:88
#4 0x80b9f15 in assert_failed (
file=0x8265f20 "/usr/src/xemacs/xemacs_21_2/src/insdel.c", line=1122,
expr=0x8265fa0 "( x) >= BI_BUF_BEG (buf) && x <= BI_BUF_Z (buf)")
at /usr/src/xemacs/xemacs_21_2/src/emacs.c:3118
#5 0x81669f4 in bytind_to_bufpos (buf=0x8320b78, x=1688246)
at /usr/src/xemacs/xemacs_21_2/src/insdel.c:1122
#6 0x81b07a2 in re_match_2_internal (bufp=0x82aa8d0, string1=0x0, size1=0,
string2=0x89fe10c ".", size2=1, pos=0, regs=0x82ab934, stop=1)
at /usr/src/xemacs/xemacs_21_2/src/regex.c:5511
#7 0x81ac796 in sys_re_search_2 (bufp=0x82aa8d0, string1=0x0, size1=0,
string2=0x89fe10c ".", size2=1, startpos=0, range=1, regs=0x82ab934,
stop=1) at /usr/src/xemacs/xemacs_21_2/src/regex.c:4074
#8 0x81b11b8 in sys_re_search (bufp=0x82aa8d0, string=0x89fe10c ".", size=1,
startpos=0, range=1, regs=0x82ab934)
at /usr/src/xemacs/xemacs_21_2/src/regex.c:3865
#9 0x81b1c23 in string_match_1 (regexp=143985756, string=143985772,
start=137233100, buf=0x8320b78, posix=0)
at /usr/src/xemacs/xemacs_21_2/src/search.c:397
#10 0x81b5c8e in Fstring_match (regexp=143985756, string=143985772,
start=137233100, buffer=137233100)
at /usr/src/xemacs/xemacs_21_2/src/search.c:420
#11 0x80bea04 in Feval (form=144168028)
at /usr/src/xemacs/xemacs_21_2/src/eval.c:3014
#12 0x80bf348 in Ffuncall (nargs=2, args=0xbfffea04)
at /usr/src/xemacs/xemacs_21_2/src/eval.c:3214
#13 0x80937db in execute_optimized_program (
program=0x8a4bab8 "=c0\t!\nB\022=c3\n＠\f=ab\004p=aa\002=c5\"\207", stack_depth=3,
constants_data=0x83e9bf8) at /usr/src/xemacs/xemacs_21_2/src/bytecode.c:745
#14 0x809339c in funcall_compiled_function (fun=138297216, nargs=2,
args=0xbfffeb64) at /usr/src/xemacs/xemacs_21_2/src/bytecode.c:517
#15 0x80bf4d0 in Ffuncall (nargs=3, args=0xbfffeb60)
at /usr/src/xemacs/xemacs_21_2/src/eval.c:3249
#16 0x80bfb8c in Fapply (nargs=2, args=0xbfffebe8)
at /usr/src/xemacs/xemacs_21_2/src/eval.c:3486
#17 0x80c27c7 in apply1 (fn=138297216, arg=143760960)
at /usr/src/xemacs/xemacs_21_2/src/eval.c:3839
#18 0x809755e in Fcall_interactively (function=138318956,
record_flag=137233100, keys=137233100)
at /usr/src/xemacs/xemacs_21_2/src/callint.c:394
#19 0x80bddc6 in Fcommand_execute (cmd=138318956, record=137233100,
keys=137233100) at /usr/src/xemacs/xemacs_21_2/src/eval.c:2652
#20 0x80fc42c in execute_command_event (command_builder=0x836ee70,
event=141870892) at /usr/src/xemacs/xemacs_21_2/src/event-stream.c:3838
#21 0x80fcfef in Fdispatch_event (event=144687836)
at /usr/src/xemacs/xemacs_21_2/src/event-stream.c:4157
#22 0x809da85 in Fcommand_loop_1 ()
at /usr/src/xemacs/xemacs_21_2/src/cmdloop.c:579
#23 0x80bc2d4 in condition_case_1 (handlers=137233196,
bfun=0x809dcc0 <command_loop_1>, barg=137233100,
hfun=0x809dd80 <cmd_error>, harg=137233100)
at /usr/src/xemacs/xemacs_21_2/src/eval.c:1640
#24 0x809df76 in command_loop_2 (dummy=137233100)
at /usr/src/xemacs/xemacs_21_2/src/cmdloop.c:256
#25 0x80bc0cc in internal_catch (tag=137304860,
func=0x809df30 <command_loop_2>, arg=137233100, threw=0x0)
at /usr/src/xemacs/xemacs_21_2/src/eval.c:1306
#26 0x809d23e in initial_command_loop (load_me=137233100)
at /usr/src/xemacs/xemacs_21_2/src/cmdloop.c:305
#27 0x80b80d5 in xemacs_21_2_b35_i686_pc_linux ()
at /usr/src/xemacs/xemacs_21_2/src/emacs.c:2155
#28 0x80b8914 in main () at /usr/src/xemacs/xemacs_21_2/src/emacs.c:2584
#29 0x403709cb in __libc_start_main (main=0x80b8810 <main>, argc=1,
argv=0xbffff254, init=0x807e500 <_init>, fini=0x822093c <_fini>,
rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbffff24c)
at ../sysdeps/generic/libc-start.c:92
--
//Markus
- 5 participants
- 5 comments
popup-mode-menu in 21.2.35
23 years, 9 months
Dmitry Yaitskov
Dmitry Yaitskov
I had Sh-f1 mapped to popup-mode-menu, to be able to invode context
menus w/out using the mouse. In 21.2.35, this stopped working - now I
get the message "popup-mode-menu must be bound to a mouse or misc-user
event". My question is - why can't I have it also assigned to a key?
And if that's a feature, how can I do what I did before? Thanks.
--
Cheers,
-Dima.
- 2 participants
- 1 comments
FontSet for XIM, dynamically changeable?
23 years, 9 months
Mike FABIAN
Mike FABIAN
The FontSet, which is used while inputting Japanese using XIM and
which is also used for the menu bar, can be selected using something
like
!! FontSet for menus when you use --with-xfs or --with-xim=xlib.
XEmacs*fontSet: -*-fixed-medium-r-normal--16-*
in .Xresources.
Is it also possible to change this FontSet later, after XEmacs has
been started?
Currently, if I change the fonts used for normal text within XEmacs at
runtime (using 'set-face-font'), the font used for XIM doesn't change.
For example if I change to a bigger font to be able to read Japanese
better, the font used for XIM still stays tiny and difficult to read.
I.e. while typing a Japanese word or phrase, pressing SPC to convert
to Kanji and selecting the correct Kanji, the characters are small.
After the conversion to Kanji is finished, the characters jump to the
size of the surrounding characters.
If the FontSet used for XIM could be changed at runtime too, this
annoying behaviour could be avoided.
--
Mike Fabian <mfabian(a)suse.de>
- 3 participants
- 3 comments
Fix tab lossage
23 years, 9 months
Andy Piper
Andy Piper
This should resume normal service. I have also fixed the elhash stuff.
andy
2000-07-31 Andy Piper <andy(a)xemacs.org>
* buffer.c (Frecord_buffer): make absolutely sure that redisplay
will acknowledge the change.
* glyphs.h: declare tab_control_order_only_changed.
* glyphs-x.c (x_tab_control_redisplay): use
tab_control_order_only_changed.
* glyphs-widget.c (tab_control_order_only_changed): new function.
* glyphs-msw.c (mswindows_tab_control_redisplay): use
tab_control_order_only_changed.
* gui.c (gui_item_equal_sans_selected): new function.
(gui_item_equal): use it.
* glyphs-msw.c (mswindows_combo_box_instantiate): deprecate
:properties in favor of :items..
* glyphs-widget.c (check_valid_item_list): rename from
check_valid_item_list_1.
(check_valid_item_list_1): renamed.
(combo_box_validate): deprecate :properties in favor of :items.
(widget_instantiate): ditto.
(tab_control_update): ditto.
(image_instantiator_combo_box): ditto.
(image_instantiator_tree_view): ditto.
(image_instantiator_tab_control): ditto.
(layout_post_instantiate): remove dead code.
* print.c (debug_print_no_newline): only write to debugger if in
WIN32_NATIVE.
* elhash.c (Fmake_hash_table): update doc string.
* event-msw.c (mswindows_wnd_proc): don't allow processing of
messages whilst in GC. This at least stops XEmacs crashing but has
the potential for wierd behaviour.
2000-07-31 Andy Piper <andy(a)xemacs.org>
* gutter-items.el (update-tab-in-gutter): deprecate :properties.
2000-07-27 Andy Piper <andy(a)xemacs.org>
* lispref/hash-tables.texi: add new hash table type.
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
- 3 participants
- 3 comments
Error with makeinfo
23 years, 9 months
Norbert Koch
Norbert Koch
Hi!
After updating from CVS (which took about an hour...) I see the
following error
makeinfo -P lispref -o ../info/lispref.info lispref/lispref.texi
makeinfo: invalid option -- P
Try `makeinfo --help' for more information.
nk＠lamia:xemacs$ makeinfo --version
GNU Makeinfo (Texinfo 3.9) 1.67
Copyright (C) 1996 Free Software Foundation, Inc.
There is NO warranty. You may redistribute this software
under the terms of the GNU General Public License.
For more information about these matters, see the files named COPYING.
Is this a makeinfo version problem which'll go away after updating or
is this a typo?
Thanks,
norbert
--
Two LITTLE black dots and one BIG black dot...nice 'n' FLUFFY!!
- 2 participants
- 1 comments
Athena widgets
23 years, 9 months
Steve Youngs
Steve Youngs
I've just noticed a little annoyance with Athena widgets and XEmacs
21.2-b35 + CVS changes to July 28. ( --with-athena=next )
Buttons aren't being displayed properly...
Stop displays as %_St
OK displays as %_
Cancel displays as %_Canc
etc etc.
I'm not 100% convinced that this has anything to do with XEmacs
because lately I've been playing around with my neXtaw and X libs. So
there's a good chance that I've fsck'd something up there.
Just wondering if anyone else is seeing this behaviour with Athena
widgets?
--
|---<Regards, Steve Youngs>-----------[GnuPG KeyID: EFD82ED2]---|
| It's a funny thing about life; if you refuse to accept |
| anything but the best, you very often get it |
|-----------------------------<mailto:youngs_s＠ozlinx.com.au>---|
- 3 participants
- 3 comments