December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

`make-annotation' fix 25 years, 11 months

Hrvoje Niksic

Adrian, Colin, could you please confirm that this patch fixes the problem? The patch disallows attaching glyphs to extents unless glyphs are of type `buffer', which prevents the crash for me. It might still be possible to muck things up by attaching an empty `buffer' glyph to an extent, and then attaching a, say, `pointer' image instance object to the glyph, but I was unable to prove it. 1998-12-14 Hrvoje Niksic <hniksic(a)srce.hr> * extents.c (set_extent_glyph_1): Make sure that the glyph we attach to the extent is valid. --- src/extents.c.orig Mon Dec 14 23:08:54 1998 +++ src/extents.c Mon Dec 14 23:17:45 1998 ＠＠ -5009,10 +5009,10 ＠＠ EXTENT extent = decode_extent (extent_obj, DE_MUST_HAVE_BUFFER); glyph_layout layout = symbol_to_glyph_layout (layout_obj); - /* Make sure we've actually been given a glyph or it's nil (meaning - we're deleting a glyph from an extent). */ + /* Make sure we've actually been given a valid glyph or it's nil + (meaning we're deleting a glyph from an extent). */ if (!NILP (glyph)) - CHECK_GLYPH (glyph); + CHECK_BUFFER_GLYPH (glyph); set_extent_glyph (extent, glyph, endp, layout); return glyph;

1 participants
0 comments

Re: [CRASH] Incorrect (make-annotation ...) vaporizes XEmacsen 21.[02] 25 years, 11 months

SL Baur

Colin Rafferty <craffert(a)ms.com> writes in xemacs-beta(a)xemacs.org: ... > I can reproduce this in a vanilla XEmacs. > Here is the Lisp code (assuming that you have a recycle2.xpm glyph). > Note that this will not happen if you use the default gc-pointer-glyph. > (if (featurep 'xpm) > (let ((file (locate-data-file "recycle2.xpm"))) > (if (condition-case error > (make-image-instance file nil > '(pointer)) > (error nil)) > (set-glyph-image gc-pointer-glyph file)))) > (make-annotation gc-pointer-glyph nil 'text) This sequence crashes on me. Fatal error: assertion failed, file redisplay-x.c, line 491, abort()

1 participants
0 comments

Re: [FAILURE] 21.0.60 linux-alpha 25 years, 11 months

Neal D. Becker

The failure was egcs-1.1.1. I recompiled with egcs-2.90.27 and it's working OK.

1 participants
0 comments

Re: pcl-cvs parser errors 25 years, 11 months

Adrian Aichner

>>>>> "nbecker" == nbecker <nbecker(a)fred.net> writes: nbecker> `pcl-cvs-version' is a variable declared in Lisp. nbecker> -- loaded from "pcl-cvs" nbecker> Value: "R-2_0-Beta_2" Neil, you could give it a try with the latest CVS module named xemacs-pcl-cvs. It works fine on WindowsNT even. I hope there will be a new package release of pcl-cvs soon. Regards, Adrian nbecker> Documentation: nbecker> pcl-cvs.el,v 1.117 1998/01/28 17:23:55 woods Exp nbecker> Parser Error: nbecker> '===================================================================' nbecker> Message: nbecker> Parser Error: 'File: math.h Status: Locally Added' nbecker> Message: nbecker> Parser Error: '' nbecker> Message: nbecker> Parser Error: ' Working revision: New file!' nbecker> Message: nbecker> Parser Error: ' Repository revision: No revision control file' nbecker> Message: nbecker> Parser Error: ' Sticky Tag: (none)' nbecker> Message: nbecker> Parser Error: ' Sticky Date: (none)' nbecker> Message: nbecker> Parser Error: ' Sticky Options: (none)' nbecker> Message: nbecker> Parser Error: ''

1 participants
0 comments

pcl-cvs parser errors 25 years, 11 months

Neal D. Becker

`pcl-cvs-version' is a variable declared in Lisp. -- loaded from "pcl-cvs" Value: "R-2_0-Beta_2" Documentation: pcl-cvs.el,v 1.117 1998/01/28 17:23:55 woods Exp Parser Error: '===================================================================' Message: Parser Error: 'File: math.h Status: Locally Added' Message: Parser Error: '' Message: Parser Error: ' Working revision: New file!' Message: Parser Error: ' Repository revision: No revision control file' Message: Parser Error: ' Sticky Tag: (none)' Message: Parser Error: ' Sticky Date: (none)' Message: Parser Error: ' Sticky Options: (none)' Message: Parser Error: ''

1 participants
0 comments

Re: [CRASH] Incorrect (make-annotation ...) vaporizes XEmacsen 21.[02] 25 years, 11 months

Adrian Aichner

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Adrian Aichner <aichner(a)ecf.teradyne.com> writes: Kyle> Repeated attempts with 21.0.60 fail to reproduce the problem Kyle> here, using i386-unknown-bsdi2.0 on a tty or under X. Please Kyle> send a C stacktrace. >> >> How do I obtain it correctly? >> >> XEmacs crashes without offering to enter the debugger under >> WindowsNT, which she normally would. Hrvoje> Why don't you run XEmacs under a debugger and look at where it is Hrvoje> exiting? Done that. Here's the CallStack: NTDLL! 77f76148() mswindows_output_display_block(window * 0x1034ae00, display_line * 0x1037f0d8, int 0, int 0, int 2, int 0, int 32, int 5, int 17) line 1262 + 20 bytes compare_display_blocks(window * 0x1034ae00, display_line * 0x102eb8d8, display_line * 0x1037f0d8, int 0, int 0, int 0, int 32, int 5, int 17) line 419 + 48 bytes output_display_line(window * 0x1034ae00, display_line_dynarr * 0x10275540, display_line_dynarr * 0x10275a60, int 3, int -1, int -1) line 659 + 41 bytes redisplay_output_window(window * 0x1034ae00) line 1315 + 25 bytes redisplay_window(Lisp_Object {...}, int 0) line 5242 + 9 bytes redisplay_frame(frame * 0x102c6800, int 0) line 5418 + 14 bytes redisplay_device(device * 0x10274c00) line 5502 + 11 bytes redisplay_without_hooks() line 5618 + 9 bytes redisplay() line 5692 Fnext_event(Lisp_Object {...}, Lisp_Object {...}) line 2239 Fcommand_loop_1() line 569 + 16 bytes command_loop_1(Lisp_Object {...}) line 494 condition_case_1(Lisp_Object {...}, Lisp_Object (Lisp_Object)* 0x0103a7be command_loop_1(Lisp_Object), Lisp_Object {...}, Lisp_Object (Lisp_Object, Lisp_Object)* 0x0103a24b cmd_error(Lisp_Object, Lisp_Object), Lisp_Object {...}) line 1640 + 7 bytes command_loop_3() line 255 + 35 bytes command_loop_2(Lisp_Object {...}) line 267 internal_catch(Lisp_Object {...}, Lisp_Object (Lisp_Object)* 0x0103a3b3 command_loop_2(Lisp_Object), Lisp_Object {...}, int * volatile 0x00000000) line 1315 + 7 bytes initial_command_loop(Lisp_Object {...}) line 304 + 25 bytes STACK_TRACE_EYE_CATCHER(int 1, char * * 0x1022ba80, char * * 0x10208100, int 0) line 1715 + 9 bytes main(int 1, char * * 0x1022ba80, char * * 0x10208100) line 2144 + 21 bytes XEMACS! mainCRTStartup + 180 bytes _start() line 165 KERNEL32! 77f1b304() And here's why: mswindows_output_display_block() in redisplay-msw.c calls abort() for 'pointer annotations: case IMAGE_MONO_PIXMAP: case IMAGE_COLOR_PIXMAP: mswindows_output_pixmap (w, dl, instance, xpos, rb->object.dglyph.xoffset, start_pixpos, rb->width, findex, cursor_start, cursor_width, cursor_height, 0); if (rb->cursor_type == CURSOR_ON) mswindows_output_cursor (w, dl, xpos, cursor_width, findex, 0, 1); break; case IMAGE_POINTER: ==> abort (); case IMAGE_SUBWINDOW: /* #### implement me */ break; case IMAGE_NOTHING: /* nothing is as nothing does */ break; Regards, Adrian

1 participants
0 comments

Re: XEmacs 21.0.60 is released 25 years, 11 months

Michael Sperber

>>>>> "KP" == lsson <Kenneth> writes: KP> I successfully compiled the XEmacs 21.0.60 on AIX 4.3, but when i tried KP> to run it on a VT220 terminal it didn't respond to pressed keys. I have KP> read that there is a problem with Emacs on AIX 4.3 (but it works fine on KP> earlier releases of AIX). Has the problem been resolved in this KP> distribution? This problem is due to a big in the libXt shipped with AIX, I believe, so there's not much we can do about it. Try building against stock X11R6. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

Re: [CRASH] Incorrect (make-annotation ...) vaporizes XEmacsen 21.[02] 25 years, 11 months

Colin Rafferty

Adrian Aichner writes: > Following line which tries to use a pointer glyph as a text annotation > crashes both XEmacs-21.0-b59 and XEmacs-21.2-b5. They vanish without > a single line of good-bye. > (make-annotation gc-pointer-glyph nil 'text) I can reproduce this in 20.4, on both Solaris and IRIX. I can also reproduce this on 21.0 (Poitou60) on IRIX (the only one that I have tried). I can reproduce this in a vanilla XEmacs. Here is the Lisp code (assuming that you have a recycle2.xpm glyph). Note that this will not happen if you use the default gc-pointer-glyph. (if (featurep 'xpm) (let ((file (locate-data-file "recycle2.xpm"))) (if (condition-case error (make-image-instance file nil '(pointer)) (error nil)) (set-glyph-image gc-pointer-glyph file)))) (make-annotation gc-pointer-glyph nil 'text) Here is the lisp backtrace: Lisp backtrace follows: # (condition-case ... . error) # (catch top-level ...) Abort Here is the stack trace: (dbx) run -vanilla Process 21984 (xemacs) terminated Process 8049 (xemacs) started CSTC version 4.2.2 SOCKS client. Default SOCKS server: bkinos.morgan.com Fatal error: assertion failed, file /ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay-x.c, line 491, abort() Process 8049 (xemacs) stopped on signal SIGABRT: Abort (see abort(3c)) (handler fatal_error_signal) at [_kill:15 +0x8,0xfaa57f8] Source (of /xlv24/patches/3312/work/irix/lib/libc/libc_n32_M4/signal/kill.s) not available for Process 8049 (dbx) where > 0 _kill(0x1f71, 0x6, 0x0, 0x0, 0x0, 0x200e6c, 0xfb512f8, 0x200e70) ["/xlv24/patches/3312/work/irix/lib/libc/libc_n32_M4/signal/kill.s":15, 0xfaa57f8] 1 _raise(0x1f71, 0x6, 0x0, 0x0, 0x0, 0x200e6c, 0xfb512f8, 0x200e70) ["/xlv24/patches/3312/work/irix/lib/libc/libc_n32_M4/signal/raise.c":25, 0xfaa5eb0] 2 _abort(0x1f71, 0x6, 0x0, 0x0, 0x0, 0x200e6c, 0xfb512f8, 0x200e70) ["/xlv24/patches/3312/work/irix/lib/libc/libc_n32_M4/gen/abort.c":47, 0xfa316ec] 3 assert_failed(file = 0x102e5f58 = "/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay-x.c", line = 491, expr = 0x103020e0 = "abort()") ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/emacs.c":2608, 0x1009e2f8] 4 x_output_display_block(w = 0x10600e00, dl = 0x1062c2d0, block = 0, start = 0, end = 46, start_pixpos = 0, cursor_start = 296, cursor_width = 5, cursor_height = 10) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay-x.c":491, 0x10235c10] 5 compare_display_blocks(w = 0x10600e00, cdl = 0x1062ead0, ddl = 0x1062c2d0, c_block = 0, d_block = 0, start_pixpos = 0, cursor_start = 296, cursor_width = 5, cursor_height = 10) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay-output.c":419, 0x101c780c] 6 output_display_line(w = 0x10600e00, cdla = 0x10617960, ddla = 0x106179a0, line = 10, force_start = -1, force_end = -1) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay-output.c":659, 0x101c87c0] 7 redisplay_output_window(w = 0x10600e00) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay-output.c":1318, 0x101caf00] More (n if no)? 8 redisplay_window(window = 274730496, skip_selected = 0) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay.c":5241, 0x101b92bc] 9 redisplay_frame(f = 0x10600000, preemption_check = 0) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay.c":5417, 0x101b9aec] 10 redisplay_device(d = 0x1051e900) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay.c":5501, 0x101ba0c4] 11 redisplay_without_hooks() ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay.c":5617, 0x101ba9c4] 12 redisplay() ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/redisplay.c":5685, 0x101bac60] 13 Fnext_event(event = 274857332, prompt = 272617476) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/event-stream.c":2238, 0x100f3fe0] 14 Fcommand_loop_1() ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/cmdloop.c":570, 0x1006e488] 15 command_loop_1(dummy = 272617476) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/cmdloop.c":494, 0x1006e098] 16 condition_case_1(handlers = 272617588, bfun = 0x1006e050, barg = 272617476, hfun = 0x1006d368, harg = 272617476) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/eval.c":1653, 0x100a3844] 17 command_loop_3() ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/cmdloop.c":256, 0x1006d550] 18 command_loop_2(dummy = 272617476) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/cmdloop.c":267, 0x1006d5b0] More (n if no)? 19 internal_catch(tag = 272695804, func = 0x1006d58c, arg = 272617476, threw = (nil)) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/eval.c":1328, 0x100a31c4] 20 initial_command_loop(load_me = 272617476) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/cmdloop.c":305, 0x1006d968] 21 xemacs_21_0_b60_mips_sgi_irix6_4(argc = 2, argv = 0x7ffb7eb4, envp = 0x7ffb7ec0, restart = 0) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/emacs.c":1705, 0x1009c488] 22 main(argc = 2, argv = 0x7ffb7eb4, envp = 0x7ffb7ec0) ["/ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/src/emacs.c":2122, 0x1009d3a8] 23 __start() ["/xlv22/ficus-jan23/work/irix/lib/libc/libc_n32_M4/csu/crt1text.s":166, 0x10041988] (dbx) Here is my Installation file: uname -a: IRIX64 sag3 6.4 02121744 IP27 /ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20/configure '--extra-verbose' '--with-gcc=no' '--compiler=/bin/cc' '--cflags=-DXTHREADS -D__BIT_TYPES_DEFINED__ -D_BSD_SIGNALS -g -OPT:Olimit=0:space=ON -n32 -mips4' '--debug' '--error-checking=all' '--gung-ho' '--with-socks' '--with-tiff=no' '--with-dialogs=athena' '--external-widget' '--x-includes=/usr/include' '--site-includes=/u/craffert/include /ms/dist/aurora/PROJ/xpm/3.4j/common/include /ms/dist/aurora/include' '--site-libraries=/u/craffert/exec/lib /ms/dist/aurora/PROJ/xpm/3.4j/exec/lib /ms/dist/aurora/lib /usr/lib32' '--package-path=~/.xemacs::~/proj/shadow/xemacs/packages::/ms/dist/fsf/PROJ/xemacs/20.4.0/exec/lib/xemacs-20.4' XEmacs 21.0-b60 "Poitou60" configured for `mips-sgi-irix6.4'. Where should the build process find the source code? /ms/user/c/craffert/proj/shadow/xemacs/cvs/xemacs-20 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/irix6-0.h' and `m/iris4d.h' What compiler should XEmacs be built with? /bin/cc -DXTHREADS -D__BIT_TYPES_DEFINED__ -D_BSD_SIGNALS -g -OPT:Olimit=0:space=ON -n32 -mips4 Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/include Where do we find X Windows libraries? Additional header files: /u/craffert/include /ms/dist/aurora/PROJ/xpm/3.4j/common/include /ms/dist/aurora/include Additional libraries: /u/craffert/exec/lib /ms/dist/aurora/PROJ/xpm/3.4j/exec/lib /ms/dist/aurora/lib /usr/lib32 Runtime library search path: /u/craffert/exec/lib:/ms/dist/aurora/PROJ/xpm/3.4j/exec/lib:/ms/dist/aurora/lib:/usr/lib32 Compiling in support for SOCKS. Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for GNU DBM. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- -- Colin

1 participants
0 comments

Re: background and foreground colors 25 years, 11 months

Jan Vroonhof

Larry Ayers <layers(a)marktwain.net> writes: > Oops! Disregard my previous message; the function face-spec-set > _is_ identical to the one in your message (in my faces.el). I > still have the behaviour I reported earlier. The function I > posted was the next one in the file (as you no doubt realized). I still think there is something weird going on. What happens when you (load "faces.el") ;; Note the .el! and THEN customize the default face using the options menu. Or else use M-x eval-defun on the face-spec-set definition. Jan

1 participants
0 comments

Re: patch to ftp://ftp.xemacs.org/pub/xemacs/contrib/gud.el 25 years, 11 months

Adrian Aichner

>>>>> "Aki" == Aki Vehtari <Aki.Vehtari(a)hut.fi> writes: Aki> ftp://ftp.xemacs.org/pub/xemacs/contrib/gud.el is Steve's XEmacs Aki> port of gud.el from Emacs 20.3. Aki> Here is patch against it fixing one bug, adding easymenu and making Aki> it work both in XEmacs and Emacs. RMS might accept easymenu change Aki> to Emacs' gud.el too, but I haven't sent this patch yet to RMS, as Aki> I want to hear your comments first. I'm lost. Is ftp://ftp.xemacs.org/pub/xemacs/contrib/gud.el the latest or is it the one in the CVS module xemacs-debug? Steven? Adrian Aki> Adrian please test this on windows. Original Emacs-20.3 gud.el had I'll give it a try, if I can make the time. Aki> a comment about path-regexp fixed for windows paths, so this might Aki> work without your patch. Aki> This has been sent both to beta and patches list. Aki> 1998-12-14 Aki Vehtari <Aki.Vehtari(a)hut.fi> Aki> * gud.el: (gud-format-command): In concat use int-to-string Aki> (gud-new-keymap): Make this work in XEmacs and Emacs Aki> (gud-make-debug-menu): Use easymenu

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta December 1998