June 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: xemacs crashes immediately on Alpha Linux 23 years, 10 months

SL Baur

Falk Hueffner <falk.hueffner(a)student.uni-tuebingen.de> writes in xemacs-beta(a)xemacs.org: ... > Building with the Compaq C compiler crashes at the same step in the > make process. It also worked (well, at least *built*) some weeks > ago. Does anybody have an idea how to proceed? If you haven't changed anything on your system, then it's definitely an XEmacs problem. XEmacs is reasonably 64 bit clean, but it's been fairly difficult getting it that way and it's easy to break and a royal pain to debug when things go wrong. You need to isolate where in the code it's crashing, then look over diffs between it used to work and now to see what has changed. Which distribution of Linux are you using? (and kernel, gcc, glibc, binutils versions, etc.)

2 participants
1 comments

xemacs crashes immediately on Alpha Linux 23 years, 10 months

Falk Hueffner

Hi, when building xemacs from CVS, it crashes at this point: [...] Loading /usr/local/src/xemacs-21.2/lisp/itimer-autosave.elc... Loading /usr/local/src/xemacs-21.2/lisp/printer.elc... Loading /usr/local/src/xemacs-21.2/lisp/toolbar.elc... Loading /usr/local/src/xemacs-21.2/lisp/scrollbar.elc... Loading /usr/local/src/xemacs-21.2/lisp/menubar.elc... Loading /usr/local/src/xemacs-21.2/lisp/dialog.elc... Loading /usr/local/src/xemacs-21.2/lisp/gutter.elc... Loading /usr/local/src/xemacs-21.2/lisp/gui.elc... Loading /usr/local/src/xemacs-21.2/lisp/mode-motion.elc... Loading /usr/local/src/xemacs-21.2/lisp/mouse.elc... Loading /usr/local/src/xemacs-21.2/lisp/select.elc... Loading /usr/local/src/xemacs-21.2/lisp/menubar-items.elc... Loading /usr/local/src/xemacs-21.2/lisp/gutter-items.elc... Loading /usr/local/src/xemacs-21.2/lisp/x-faces.elc... Loading /usr/local/src/xemacs-21.2/lisp/x-iso8859-1.elc... Loading /usr/local/src/xemacs-21.2/lisp/x-mouse.elc... Loading /usr/local/src/xemacs-21.2/lisp/x-select.elc... Loading /usr/local/src/xemacs-21.2/lisp/x-scrollbar.elc... Loading /usr/local/src/xemacs-21.2/lisp/x-misc.elc... Loading /usr/local/src/xemacs-21.2/lisp/x-init.elc... Loading /usr/local/src/xemacs-21.2/lisp/toolbar-items.elc... Loading /usr/local/src/xemacs-21.2/lisp/x-win-xfree86.elc... Loading /usr/local/src/xemacs-21.2/lisp/x-win-sun.elc... Loading /usr/local/src/xemacs-21.2/lisp/tty-init.elc... Loading /usr/local/src/xemacs-21.2/lisp/fontl-hooks.elc... Loading /usr/local/src/xemacs-21.2/lisp/auto-show.elc... Loading /usr/local/src/xemacs-21.2/lisp/loadhist.elc... Loading /usr/local/src/xemacs-21.2/lisp/loaddefs.elc... Loading site-load... Finding pointers to doc strings... Finding pointers to doc strings...done Dumping under the name xemacs Testing for Lisp shadows ... Fatal error (11). 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/local/src/xemacs-21.2/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: intern("paths-el-original-news-inews-program") (let ((origsym ...)) (if (running-temacs-p) (progn ... ...) (and ... ...))) # bind (value var) (lambda (var value) (let (...) (if ... ... ...)))(news-inews-program "inews") funcall((lambda (var value) (let (...) (if ... ... ...))) news-inews-program "inews") # bind (l) (let ((l ...)) (funcall l (quote news-inews-program) (cond ... ... ... ... ...)) (funcall l (quote mh-progs) (cond ... ... ... ... ...)) (funcall l (quote mh-libs) (cond ... ... ... ...)) (funcall l (quote rmail-spool-directory) (cond ... ... ... ... ... ...)) (funcall l (quote sendmail-program) (cond ... ... ... ...)) (funcall l (quote remote-shell-program) (cond ... ... ... ... ... ... ... ... ... ... ... ... ...)) (funcall l (quote manual-program) (if ... "/usr/ucb/man" "/usr/bin/man")) (funcall l (quote directory-abbrev-alist) (when ... ...))) initialize-xemacs-paths() normal-top-level() # (condition-case ... . error) # (catch top-level ...) make[1]: *** [xemacs] Segmentation fault (core dumped) make[1]: *** Deleting file `xemacs' make[1]: Leaving directory `/usr/local/src/xemacs-21.2/src' make: *** [src] Error 2 The makefile seems to be running 'xemacs -batch -vanilla -f list-load-path-shadows' (btw why the ＠ in the Makefile? I want to see what it is doing...). If I try this with gdb, I get: gdb ./xemacs GNU gdb 19990928 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 "alphaev56-unknown-linux-gnu"...run (gdb) run -batch -vanilla -f list-load-path-shadows Starting program: /usr/local/src/xemacs-21.2/src/./xemacs -batch -vanilla -f list-load-path-shadows Program received signal SIGSEGV, Segmentation fault. 0x120236a40 in Fintern (string=4839586056, obarray=2199023435792) at symbols.c:175 175 } (gdb) bt #0 0x120236a40 in Fintern (string=4839586056, obarray=2199023435792) at symbols.c:175 #1 0x1200b07ec in Feval (form=4839052928) at eval.c:3014 #2 0x1200aa57c in Flet (args=4839586056) at eval.c:915 #3 0x1200b0630 in Feval (form=4839052880) at eval.c:2986 #4 0x1200b3134 in funcall_lambda (fun=4839052784, nargs=2, args=0x11fffe8d0) at eval.c:768 #5 0x1200b1928 in Ffuncall (nargs=544618760, args=0x11fffe8c8) at eval.c:3257 #6 0x1200b0a7c in Feval (form=4839053984) at eval.c:3040 #7 0x1200aa81c in Flet (args=4839586056) at eval.c:768 #8 0x1200b0630 in Feval (form=4839052736) at eval.c:2986 #9 0x1200b3134 in funcall_lambda (fun=4838776744, nargs=0, args=0x11fffef28) at eval.c:768 #10 0x1200b1928 in Ffuncall (nargs=544618760, args=0x11fffef20) at eval.c:3257 #11 0x1200681b0 in execute_optimized_program (program=0x120763908 "\b", stack_depth=541533512, constants_data=0x120671220) at bytecode.c:747 #12 0x120067ae8 in funcall_compiled_function (fun=4838590504, nargs=0, args=0x11ffff058) at bytecode.c:519 #13 0x1200b0d1c in Feval (form=4837685680) at eval.c:3073 #14 0x1200abed0 in condition_case_1 (handlers=4839586056, bfun=0x1200afb40 <Feval>, barg=4837685680, hfun=0x1200797c0 <cmd_error>, harg=4836500808) at eval.c:1640 #15 0x1200798c8 in top_level_1 (dummy=4839586056) at cmdloop.c:206 #16 0x1200b94bc in internal_catch (tag=4839586056, func=0x120079880 <top_level_1>, arg=4836500808, threw=0x0) at eval.c:1306 #17 0x1200782ac in initial_command_loop (load_me=4839586056) at cmdloop.c:285 #18 0x1200a5420 in xemacs_21_2_b34_alphapca56_unknown_linux (argc=5, argv=0x11ffff6c8, envp=0x12012b460, restart=0) at emacs.c:2146 #19 0x1200a86e4 in main (argc=544618760, argv=0x120472548, envp=0x12012b460) at emacs.c:2575 which doesn't look too convincing. The configuration for this was: uname -a: Linux borkum 2.2.14 #1 Tue May 30 01:00:41 CEST 2000 alpha unknown ./configure XEmacs 21.2-b34 "Molpe" configured for `alphapca56-unknown-linux'. Compilation / Installation: Source code location: /usr/local/src/xemacs-21.2 Installation prefix: /usr/local Operating system description file: `s/linux.h' Machine description file: `m/alpha.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Wpointer-arith -Winline -Wmissing-prototypes -Wshadow Relocating allocator for buffers: no GNU version of malloc: no - The GNU allocators don't work with this system configuration. Window System: Compiling in support for the X window system: - X Windows headers location: /usr/X11R6/include - X Windows libraries location: /usr/X11R6/lib - Handling WM_COMMAND properly. Compiling in support for the Athena widget set: - Athena headers location: X11/Xaw - Athena library to link: Xaw Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Using Athena native widgets. TTY: Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Images: Compiling in support for GIF images (builtin). Compiling in support for XPM images. Compiling in support for PNG images. Compiling in support for JPEG images. Compiling in support for TIFF images. Sound: Compiling in support for sound (native). Compiling in support for ESD (Enlightened Sound Daemon). Databases: Compiling in support for Berkeley database. Internationalization: Mail: Compiling in support for "dot-locking" mail spool file locking method. Other Features: Compiling in support for dynamic shared object modules. Compiling in support for extra debugging code. 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: --------------------------------------------------------- Building with the Compaq C compiler crashes at the same step in the make process. It also worked (well, at least *built*) some weeks ago. Does anybody have an idea how to proceed? Falk

3 participants
2 comments

Re: The XEmacs 21.1 tarballs on ftp.xemacs.org are bad 23 years, 10 months

Vin Shelton

Yes, I just noticed this Tuesday night. I will issue 21.1.11 soon, I guess. - vin >>>>> On 08 Jun 2000, SL Baur <steve(a)turbolinux.co.jp> said: sb> The main tarballs contain many empty directories in lisp/. I think sb> the simplest fix is to add the line: sb> checkout -ko -P sb> to ~/.cvsrc in the account being used to generate them. In the sb> meantime, it might be a good idea to do a 21.1.11 quickly. Quail is sb> definitely broken by the current state. sb> [Thanks to Maxime Froment for bringing this to my attention.]

1 participants
0 comments

The XEmacs 21.1 tarballs on ftp.xemacs.org are bad 23 years, 10 months

SL Baur

The main tarballs contain many empty directories in lisp/. I think the simplest fix is to add the line: checkout -ko -P to ~/.cvsrc in the account being used to generate them. In the meantime, it might be a good idea to do a 21.1.11 quickly. Quail is definitely broken by the current state. [Thanks to Maxime Froment for bringing this to my attention.]

1 participants
0 comments

Re: [ANNOUNCE] New XEmacs Mirror Sites 23 years, 10 months

Jason R Mastaler

James Achtung Crippen <james(a)fredbox.com> writes: > Has anyone considered contacting the people at Walnut Creek CDROM > for a mirror site? They are one of the "fastest mirror sites in the > West" in my experience. Yes, I contacted ftp.cdrom.com in October to see if they were interested in mirroring XEmacs but never received a response. Since then however, I think we have accumulated quite a nice collection of distributed and well-connected mirror sites. See <http://www.xemacs.org/Download/>

1 participants
0 comments

directory-files and case search 23 years, 10 months

Didier Verna

Since this function can perform matching based on regular expressions, it should handle the case folding facilities offered to the programmer. The most logical and natural way to achieve this is IMO to make it respect the variable `case-fold-search'. The drawback is that it might then be affected by some current-buffer settings (case-fold-search itself, plus some other stuff, see `fast_string_match'). If we do this, we take the risk of breaking existing code. Of course, I'm willing to fix all core and external packages that we distribute. But do we want to do this change ? Another alternative would be a new flag, but I hate this. This function has already too many insane flags, and the long term solution would probably be to to write a better designed replacement for it. Comments ? -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠lrde.epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

1 participants
0 comments

ring-insert, pcl-cvs, and vc-cc 23 years, 10 months

Raymond Toy

Previously, Adrian mentioned the problem with ring-insert and pcl-cvs v2_9_9 where pcl-cvs was calling (ring-insert vc-comment-ring <string>) but vc-comment-ring was nil. I didn't see any patch or comments in the mail archives so here is my patch. Without it, I can't commit anything with pcl-cvs. It's a bug in vc-cc/vc.el for not initializing vc-comment-ring to a ring. Ray Changelog entry: 2000-06-07 Raymond Toy <toy(a)rtp.ericsson.se> * vc.el (vc-comment-ring): Initialize vc-comment-ring to a ring instead NIL. Patch for vc-cc/vc.el: --- vc.el~ Wed Aug 12 06:26:21 1998 +++ vc.el Wed Jun 7 09:28:58 2000 ＠＠ -218,7 +218,7 ＠＠ (defconst vc-name-assoc-file "VC-names") -(defvar vc-comment-ring nil) +(defvar vc-comment-ring (make-ring vc-maximum-comment-ring-size)) (defvar vc-comment-ring-index nil) (defvar vc-last-comment-match nil) (defvar vc-window-config nil)

1 participants
0 comments

Re: [Applied Patches 21.2] final trivial typo fixes for man/xemacs 23 years, 10 months

Adrian Aichner

>>>>> "APA" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: APA> This rounds up my ispell-fascilitated fixes for typos in all Sorry for my fascist typo above. Obviously I meant to write ispell-facilitated. Maybe I should start using ispell myself :-) Best regards, Adrian APA> man/xemacs/*.texi files.

1 participants
0 comments

RE: Dynamic Modules under NT 23 years, 10 months

Andrew Begel

> -----Original Message----- > From: Craig Lanning [mailto:CraigL＠DyCon.com] > Sent: Saturday, June 03, 2000 11:48 AM > To: Andrew Begel > Cc: 'xemacs-nt(a)xemacs.org'; 'xemacs-beta(a)xemacs.org'; Marat > Boshernitsan > Subject: Re: Dynamic Modules under NT > > >There are three ways to make XEmacs compile on Windows: gcc > with cygwin, gcc > >no cygwin, and MSVC++. I've gotten all three to work, though > I prefer gcc no > >cygwin and MSVC++, since that allows one to use DLLs > >Now, the more annoying bits. In order to compile DLLs for > Windows, you need > >to resolve all symbols at static link time. This means if a DLL needs > >symbols from the application which is loading it, those > symbols must be > >munged into an import library for the DLL to link with. In > addition, those > >same symbols must be munged into an export library for the > application to > >link with. Yes, that's right, temacs needs to be linked with > an export > >library that must "predict" what symbols any DLL might use. > > The normal way to make this work would be to define an API that looks > something like this: > > 1. Each DLL is required to export a set of specific functions with > specific names so that the loading application (XEmacs in > this case) can > hook everything up. This is all taken care of by the standardized XEmacs dynamic-module interface. Dynamic modules must define several functions and constants for Xemacs to find it and properly load it. These must be exported from the DLL, so it wouldn't be too hard to create a .h file (with ellcc or make the user do it) with #if defined(WIN32) && defined(HAVE_SHLIB) #define EXPORT __declspec(dllexport) #define IMPORT __declspec(dllimport) #else #define EXPORT #define IMPORT #endif (or put that in symdll.h or somewhere nice). Then make the user put EXPORT in front of all of these standard symbols (defs_of_<module>, syms_of_<module>, etc.) > > 2. Each DLL can expect the application (XEmacs in this case) > to export a > set of specific functions with specific names so that the DLL can gain > access to those aspects of the application that it needs. I needed these: Qt DATA message defsubr dumpopaque Qnil DATA staticpro defvar_magic assert_failed make_uninit_string Fbuffer_substring Fcons Ffind_face Fintern alloc_lcrecord gcprolist DATA print_readably DATA signal_simple_error write_c_string boolean_specifier_methods DATA display_table_specifier_methods DATA image_specifier_methods DATA integer_specifier_methods DATA generic_specifier_methods DATA natnum_specifier_methods DATA toolbar_specifier_methods DATA lrecord_implementations_table DATA lrecord_markers DATA lrecord_type_count DATA As you can see, some of them are symbols, some are functions... You need a macro like this: #if defined(WIN32) && defined(HAVE_SHLIB) #ifdef BUILDING_XEMACS #define EXTERNAL __declspec(dllexport) #endif #ifdef BUILDING_MODULE #define EXTERNAL __declspec(dllimport) #endif #if defined(BUILDING_XEMACS) && defined(BUILDING_MODULE) #error "BUILDING XEMACS and BUILDING_MODULE both defined!" #endif #if !defined(BUILDING_XEMACS) && !defined(BUILDING_MODULE) #define EXTERNAL #endif #else #define EXTERNAL #endif and then put EXTERNAL in front of all Xemacs symbols and functions that potentially may be used by dynamic modules. Since I couldn't hope to guess what a module may or may not use, I'd just as soon as put EXTERNAL in front of every non-static symbol. If you do this, you won't need to define the export library for XEmacs (just #define BUILDING_XEMACS), though you will still need the import library for compiling the DLL (where you'll #define BUILDING_MODULE). andy > > These kinds of mechanisms eliminate the need to do what you > describe below. > From your description, I suspect that some significant work > needs to be > done with regard to defining the API. > > What would be extremely useful is if you could make a list of > the kinds of > things that you need access to in the application and another > list of the > kinds of things that you expect to provide to the > application. This kind > of information would be useful in beginning the definition of the API. > > Craig Lanning >

3 participants
2 comments

what are those dir filename variants for ? 23 years, 10 months

Didier Verna

Are all these cases for the dir filename really needed ? They're introducing several inconsistencies in info.el, but before fixing them (and numerous other bugs), I'd like to be sure we need them. ,---- | ;; Try several variants of specified name. | ;; Try upcasing, appending `.info', or both. | [...] | (progn (setq file (expand-file-name "dir" truename)) | (file-attributes file)) | (progn (setq file (expand-file-name "DIR" truename)) | (file-attributes file)) | (progn (setq file (expand-file-name "dir.info" truename)) | (file-attributes file)) | (progn (setq file (expand-file-name "DIR.INFO" truename)) | (file-attributes file)) | (progn (setq file (expand-file-name "localdir" truename)) | (file-attributes file)) `----- -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠lrde.epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

3 participants
2 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 2000