June 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Bug Report: NT XEmacs, Buffers submenu 25 years, 5 months

Norbert Koch

Steven Webster <swebster(a)cadence.com> writes: > Going to the options menu and selecting "Submenu for Buffers Menu" > XEmacs will then crash consistently. I can send a Dr Watsons report > if that helps. Hm, I can't reproduce this here XEmacs 21.2 (beta16) "Sumida" [Lucid] (i586-pc-win32, Mule) of Thu Jun 17 1999 on KEATS Can you build a debug version? norbert.

1 participants
0 comments

Bug Report: NT XEmacs, Buffers submenu 25 years, 5 months

Steven Webster

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 (beta15) "Sakuragawa" [Lucid] (i586-pc-win32) of Sat Jun 05 1999 on NEVERYON configured using `configure UNKNOWN' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: Going to the options menu and selecting "Submenu for Buffers Menu" XEmacs will then crash consistently. I can send a Dr Watsons report if that helps. Recent keystrokes: misc-user Recent messages (most recent first): Loading mail-abbrevs... Loading emacsbug...done Loading emacsbug... Paren mode is blink-paren Loading paren...done Loading paren... Desktop loaded. Setting JDE variables to startup values... 14_June_99.txt has auto save data; consider M-x recover-file Setting JDE variables to startup values... -- Steven Webster mailto:swebster＠cadence.com Cadence Design Systems Telephone: +44 1506 596122 Livingston, Scotland http://www.cadence.com/

1 participants
0 comments

This is the future 25 years, 5 months

SL Baur

I have put a rough copy of the new ps-print on ftp.xemacs.org for comments and review. ftp://ftp.xemacs.org/pub/xemacs/beta/testing/mule-ps-print.tar.gz If you are working with 21.2 or have concerns about the role of Mule in XEmacs, please download, look at, bytecompile and comment. To bytecompile with a non-Mule XEmacs 21.2 do xemacs -vanilla -batch -eval "(setq leading-code-private-21 0)" \ -eval "(push \"$(pwd)\" load-path)" -f batch-byte-compile *.el The resulting elcs will not run. To bytecompile with XEmacs/Mule 21.2 do: xemacs -vanilla -batch -eval "(push \"$(pwd)\" load-path)" \ -f batch-byte-compile *.el To make it print something with multibyte characters, examine and change the value of `ps-multibyte-buffer'. -- 窓番号を入力してください

2 participants
1 comments

Re: Changing fonts from menu causes error 25 years, 5 months

Jan Vroonhof

rpluim(a)bigfoot.com writes: > changing the font family from the menus causes "Wrong type argument: > number-char-or-marker-p, nil" to be signalled in > font-menu-set-font. The following patch fixes it for me, but I don't > know if it's the right fix. It seems correct. Could you make up all full patch (Changelog etc) for xemacs-patches ? Jan -- Jan Vroonhof http://www.math.ethz.ch/~vroonhof/ Mathematik, vroonhof ＠ math.ethz.ch HG E16, ETH-Zentrum, Tel: +41-1-6325456/25154 Raemistrasse 101, CH-8092 Zuerich. Fax: +41-1-6321085

1 participants
0 comments

Re: dealing with strict aliasing rules 25 years, 5 months

Jan Vroonhof

Valdis.Kletnieks(a)vt.edu writes: > If I remember correctly, the aliasing problems cropped up in alloc.c. > I was in the process of rebuilding to test, but I just realized that > (a) it's 2:30Am, and (b) as a result, I compiled with '-O3 -qstrict' > where 'strict' tells the optimizer to not get into massive code > optimizations that may have an impact on program logic (which probably > inhibits most optimizations that ansialias would allow). If you can get the problem at a more normal time, could you check whether --with-union-type helps? Jan

1 participants
0 comments

Re: Build failure, xemacs-21.1.2 on rh6-based linux-alpha-unknown 25 years, 5 months

Jan Vroonhof

acs(a)ne.mediaone.net writes: > I think we should fix our code. We should take the effort to make > our code standards-compliant. Besides the optimization can > apparently be a performance win; therefore I'm not in favor of > -fno-strict-aliasing. The problem this that this will likely involve --with-union-type and compilers are known to produce horrible code for that. Jan

1 participants
0 comments

Build failure, xemacs-21.1.3 on Debian 2.1-based linux-i386-unknown 25 years, 5 months

Stephen J. Turnbull

Sigh. Debian Linux 2.1 or so "potato" all packages current 1999-06-14 Linux kernel: 2.2.5 (local config) GCC version: egcs-2.91.66 libc version: /lib/libc.so.6 -> libc-2.1.1.so libX11 version: XFree86 3.3.3.1 Debian release 8 temacs dies in update-elc with "Segmentation fault (core dumped)" and no Lisp backtrace (for reasons which will be obvious). Installation[1], then C backtrace[2]. The problems seems to be with `--use-union-type'; I've tried several variations on optimization level and --no-strict-aliases (which shouldn't matter since my egcs isn't breaking ledge) on 21.1.2, and the --use-union-type=yes builds all crashed, the --use-union-type=no builds did not (but I had problems with my CVS update, so take that with a grain of salt). Crashed were always crashed in Fintern(). Without --use-union-type=yes, the build completes and XEmacs is usable. Installation[3] attached at end. I fixed a problem with the PNG library installation so it got autorecognized; I'll go back and rebuild with '--use-union-type=yes' and PNG if anybody thinks it matters. Footnotes: [1] uname -a: Linux tanko 2.2.5 #5 Tue May 11 23:10:39 JST 1999 i586 unknown ./configure '--prefix=/playpen/gnu' '--exec-prefix=/playpen/gnu/plat' '--with-mule' '--with-xim=xlib' '--with-sound=both' '--debug' '--use-union-type=yes' '--cflags=-g -O3 -fno-caller-saves -Wall -Wno-switch' XEmacs 21.1-p3 "Acadia" configured for `i586-pc-linux'. Where should the build process find the source code? /playpen/src/xemacs-21 What installation prefix should install use? /playpen/gnu What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -fno-caller-saves -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) 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/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. -------------------------------------------------------------------- WARNING: Compiling without PNG image support. WARNING: You should strongly consider installing the PNG libraries. WARNING: Otherwise certain images and glyphs may not display. WARNING: (a copy may be found in ftp://ftp.xemacs.org/pub/xemacs/aux) -------------------------------------------------------------------- Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in both network and native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Compiling in support for Canna on Mule. 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 the union type for Lisp_Objects. Using Lisp_Objects with minimal tagbits. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. [2] GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... Core was generated by `./temacs -batch -l /playpen/src/xemacs-21/src/../lisp/update-elc.el'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/nfslock.so.0...done. Reading symbols from /usr/lib/libaudio.so.2...done. Reading symbols from /usr/lib/libcanna.so.1...done. Reading symbols from /usr/lib/libRKC.so.1...done. Reading symbols from /usr/X11R6/lib/Xaw3d/libXaw.so.6...done. Reading symbols from /usr/lib/libcompface.so.1...done. Reading symbols from /usr/lib/libtiff.so.3...done. Reading symbols from /usr/lib/libjpeg.so.62...done. Reading symbols from /usr/lib/libz.so.1...done. Reading symbols from /usr/X11R6/lib/libXpm.so.4...done. Reading symbols from /usr/X11R6/lib/libXmu.so.6...done. Reading symbols from /usr/X11R6/lib/libXt.so.6...done. Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Reading symbols from /usr/X11R6/lib/libSM.so.6...done. Reading symbols from /usr/X11R6/lib/libICE.so.6...done. Reading symbols from /lib/libdl.so.2...done. Reading symbols from /lib/libdb.so.3...done. Reading symbols from /lib/libncurses.so.4...done. Reading symbols from /lib/libm.so.6...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. #0 Fintern (str={gu = {type = Lisp_Type_Record, val = 34049556}, s = { bits = 0, val = 68099112}, u = {bits = 0, val = 68099112}, ui = 136198224, i = 136198224, v = 0x81e3850, cv = 0x81e3850}, obarray={ gu = {type = Lisp_Type_Record, val = 34505237}, s = {bits = 0, val = 69010474}, u = {bits = 0, val = 69010474}, ui = 138020948, i = 138020948, v = 0x83a0854, cv = 0x83a0854}) at symbols.c:197 197 if (SYMBOLP (*ptr)) (gdb) where #0 Fintern (str={gu = {type = Lisp_Type_Record, val = 34049556}, s = { bits = 0, val = 68099112}, u = {bits = 0, val = 68099112}, ui = 136198224, i = 136198224, v = 0x81e3850, cv = 0x81e3850}, obarray={ gu = {type = Lisp_Type_Record, val = 34505237}, s = {bits = 0, val = 69010474}, u = {bits = 0, val = 69010474}, ui = 138020948, i = 138020948, v = 0x83a0854, cv = 0x83a0854}) at symbols.c:197 #1 0x8172785 in defsymbol (location=0x83760f0, name=0x81cf40d "t") at symbols.c:3201 #2 0x816f5c2 in init_symbols_once_early () at symbols.c:3193 #3 0x80ace90 in xemacs_21_1_p3_i586_pc_linux (argc=4, argv=0xbffffb74, envp=0xbffffb88, restart=0) at emacs.c:844 #4 0x80aee41 in main (argc=4, argv=0xbffffb74, envp=0xbffffb88) at emacs.c:2069 (gdb) quit [3] uname -a: Linux tanko 2.2.5 #5 Tue May 11 23:10:39 JST 1999 i586 unknown ./configure '--prefix=/playpen/gnu' '--exec-prefix=/playpen/gnu/plat' '--with-mule' '--with-xim=xlib' '--with-sound=both' '--debug' '--cflags=-g -O3 -fno-caller-saves -Wall -Wno-switch' XEmacs 21.1-p3 "Acadia" configured for `i586-pc-linux'. Where should the build process find the source code? /playpen/src/xemacs-21 What installation prefix should install use? /playpen/gnu What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -fno-caller-saves -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) 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/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib 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 TIFF image handling. Compiling in support for X-Face message headers. Compiling in both network and native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Compiling in support for Canna on Mule. 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. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."

1 participants
0 comments

Changing fonts from menu causes error 25 years, 5 months

Robert Pluim

in XEmacs 21.2 (beta16) "Sumida" [Lucid] (i586-pc-linux) of Mon Jun 14 1999 on ltrpluim changing the font family from the menus causes "Wrong type argument: number-char-or-marker-p, nil" to be signalled in font-menu-set-font. The following patch fixes it for me, but I don't know if it's the right fix. Robert Index: font-menu.el =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/Attic/font-menu.el,v retrieving revision 1.1.2.3 diff -u -w -u -r1.1.2.3 font-menu.el --- font-menu.el 1999/06/11 03:04:55 1.1.2.3 +++ font-menu.el 1999/06/17 16:49:41 ＠＠ -400,7 +400,7 ＠＠ (list :family family :size (concat (int-to-string - (/ size + (/ (or size from-size) (specifier-instance font-menu-size-scaling (selected-device)))) "pt"))) -- The above are my opinions. Take them or leave them.

1 participants
0 comments

Re: Build failure, xemacs-21.1.2 on rh6-based linux-alpha-unknown 25 years, 5 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > int f() { > a_union t; > t.d = 3.0; > return t.i; > } > > The practice of reading from a different union member than the > one most recently written to (called "type-punning") is common. > Even with `-fstrict-aliasing', type-punning is allowed, > provided the memory is accessed through the union type. So, the > code above will work as expected. However, this code might not: > > int f() { > a_union t; > int* ip; > t.d = 3.0; > ip = &t.i; > return *ip; > } This looks insane. Am I misreading it, or does it really say that `*(&t.i)' is different than `t.i'? Also, why should union type variables be any different than other variables in this regard? For instance: int f() { int a; int *ip; a = 10; ip = &a; return *ip; } How is this any different than what is done above? > "everybody has fixed their code already because other compilers have > been doing this optimization for ages" If the last is really the case, then we indeed have nothing to worry about. XEmacs has compiled and run on non-Gcc compilers for ages. *If* the last is really the case.

4 participants
4 comments

Re: 21.1.3: you-are-trapped-in-a-twisty-maze-of-cons-cells-all-alike 25 years, 5 months

Karl M. Hegbloom

I've seen that debugger loop. It happens when I set debug on error to true, then hit an error. If I run with -vanilla, it doesn't happen. I have not tried to see what's causing it.

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 June 1999