January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

XEmacs 21.2 "Apollo" (mips-sgi-irix6.5, Mule) crash in realpath.c 25 years, 3 months

Remek Trzaska

I had been writing a message in gnus, and suddenly: Core was generated by `xemacs-21.2-b6'. Program terminated with signal 6, Abort. Reading symbols from /usr/lib32/libXm.so.1...done. <snip> Reading symbols from /usr/lib32/libgen.so...done. #0 0xfa40e80 in _kill () at realpath.c:191 I'm keeping the core file around for a while. Remek -- Remek Trzaska http://www.npac.syr.edu/users/remek Research Scientist Northeast Parallel Architectures Center at Syracuse University, NY

1 participants
0 comments

package-get-custom broken? 25 years, 3 months

Andy Piper

I've been playing around with b62 and I can't update packages using Manage Pakcages->Using custom->update. I get the error - "cannot open load-file package-get-custom". The ui stuff works fine. Also under nt I see List & Installl instead of List & Install andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

1 participants
0 comments

Mail delivery failed: returning message to sender 25 years, 3 months

Mail Delivery System

This message was created automatically by mail delivery software. A message that you sent could not be delivered to all of its recipients. The following address(es) failed: steveb(a)camelot-soft.com: SMTP error from remote mailer after RCPT TO: <steveb(a)camelot-soft.com>: host mail-fw.camelot-soft.com [210.160.150.241]: 550 ... User unknown ------ This is a copy of the message, including all the headers. ------ Return-path: <nbecker(a)hns.com> Received: from nbecker by hns.com with local (Exim 2.10 #1) id 0zxXaE-0001B5-00; Tue, 5 Jan 1999 09:35:46 -0500 To: Steven Baur <steveb(a)camelot-soft.com> Cc: xemacs-beta(a)xemacs.org Subject: update mailcrypt? References: <199901052121.NAA24053(a)camelot-soft.camelot-soft.com> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: nbecker(a)fred.net Date: 05 Jan 1999 09:35:46 -0500 In-Reply-To: Steven Baur's message of "Tue, 5 Jan 1999 13:21:39 -0800 (PST)" Message-ID: <x88g19p3hz1.fsf(a)nbeckerpc.hns.com> Lines: 2 X-Mailer: Gnus v5.6.45/XEmacs 21.0(beta61) - "Poitou61" Sender: <nbecker(a)hns.com> I'd like to see a newer mailcrypt. 3.5b7 supports gnupg which is why I use it.

1 participants
0 comments

update mailcrypt? 25 years, 3 months

Neal D. Becker

I'd like to see a newer mailcrypt. 3.5b7 supports gnupg which is why I use it.

1 participants
0 comments

Re: more search/case improvements in replace.el 25 years, 3 months

Hrvoje Niksic

Didier Verna <verna(a)inf.enst.fr> writes: > improvements a while ago. The length of the patch is mainly a matter > of indentation. Perhaps it is worth documenting those improvements > in the NEWS file too ? Yes. Interestingly enough, FSF Emacs made the same change.

1 participants
0 comments

XEmacs 21.0.60 core dumps on FreeBSD 2.2.6 25 years, 3 months

Richard Coleman

After getting a core dump with 21.2.8, I thought I would try 21.0.60 and see if I had better luck. I also get a core dump with this version. I don't think it's my machine, since I just built 20.4 as well, and it works fine. I've attached a lisp backtrace, a gdb backtrace, and the Installation file. -- Richard Coleman coleman(a)math.gatech.edu Fatal error: assertion failed, file window.h, line 245, RECORD_TYPEP (_obj, lrecord_window) || MARKED_RECORD_P (_obj) Fatal error (6). Your files have been auto-saved. Use `M-x recover-session' to recover them. 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 /home/rcoleman/xemacs/xemacs-21.0.60/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: redisplay-echo-area() # bind (inhibit-read-only zmacs-region-stays stdout-p frame message) raw-append-message("Error in init file: Symbol's function definition is void: display-time" #<x-frame "emacs" 0x8fd> nil) # bind (stdout-p frame message label) append-message(message "Error in init file: Symbol's function definition is void: display-time" nil nil) # bind (stdout-p frame message label) display-message(message "Error in init file: Symbol's function definition is void: display-time") # bind (str args fmt) message("Error in init file: %s" "Symbol's function definition is void: display-time") byte-code("..." [message "Error in init file: %s" error-message-string error display-warning initialization format "An error has occurred while loading %s:\n\n%s\n\nTo ensure normal operation, you should investigate the cause of the error\nin your initialization file and remove it. Use the `-debug-init' option\nto XEmacs to view a complete error backtrace." user-init-file t init-file-had-error] 7) # bind (error debug-on-error debug-on-error-from-init-file debug-on-error-should-be-set debug-on-error-initial) load-init-file() # bind (command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) (gdb) bt #0 0x203e7b61 in ?? () #1 0x44743 in fatal_error_signal (sig=6) at emacs.c:262 #2 0xefbfdfdc in ?? () #3 0x46f5b in assert_failed (file=0x11a87c "window.h", line=245, expr=0x11a83e "RECORD_TYPEP (_obj, lrecord_window) || MARKED_RECORD_P (_obj)") at emacs.c:2608 #4 0x12d696 in Fredisplay_echo_area () at window.h:245 #5 0x4d50a in funcall_recording_as (recorded_as=-1607563140, nargs=0, args=0xefbfc3bc) at eval.c:3197 #6 0x4d785 in Ffuncall (nargs=1, args=0xefbfc3bc) at eval.c:3238 #7 0x198a6 in Fbyte_code (bytestr=1612954684, vector=-2145141644, maxdepth=5) at bytecode.c:416 #8 0x4e6f3 in funcall_lambda (fun=539213024, nargs=3, arg_vector=0xefbfc584) at eval.c:3597 #9 0x4d691 in funcall_recording_as (recorded_as=-1607016668, nargs=3, args=0xefbfc580) at eval.c:3214 #10 0x4d785 in Ffuncall (nargs=4, args=0xefbfc580) at eval.c:3238 #11 0x198a6 in Fbyte_code (bytestr=1612954536, vector=-2145141796, maxdepth=4) at bytecode.c:416 #12 0x4e6f3 in funcall_lambda (fun=539212800, nargs=4, arg_vector=0xefbfc6e8) at eval.c:3597 #13 0x4d691 in funcall_recording_as (recorded_as=-1607565844, nargs=4, args=0xefbfc6e4) at eval.c:3214 #14 0x4d785 in Ffuncall (nargs=5, args=0xefbfc6e4) at eval.c:3238 #15 0x198a6 in Fbyte_code (bytestr=1612954916, vector=-2145141440, maxdepth=5) at bytecode.c:416 #16 0x4e6f3 in funcall_lambda (fun=539213152, nargs=2, arg_vector=0xefbfc888) at eval.c:3597 #17 0x4d691 in funcall_recording_as (recorded_as=-1607565796, nargs=2, args=0xefbfc884) at eval.c:3214 #18 0x4d785 in Ffuncall (nargs=3, args=0xefbfc884) at eval.c:3238 #19 0x198a6 in Fbyte_code (bytestr=1612955216, vector=-2145141124, maxdepth=4) at bytecode.c:416 #20 0x4e6f3 in funcall_lambda (fun=539213476, nargs=2, arg_vector=0xefbfca14) at eval.c:3597 #21 0x4d691 in funcall_recording_as (recorded_as=-1607572396, nargs=2, args=0xefbfca10) at eval.c:3214 #22 0x4d785 in Ffuncall (nargs=3, args=0xefbfca10) at eval.c:3238 #23 0x198a6 in Fbyte_code (bytestr=1613020268, vector=-2145076068, maxdepth=7) at bytecode.c:416 #24 0x4ce3c in Feval (form=1076149340) at eval.c:3063 #25 0x4a6e3 in run_condition_case_handlers (val=1078148508, var=-1607671708) at eval.c:758 #26 0x4a846 in condition_case_3 (bodyform=1076149240, var=-1607671708, handlers=1076149316) at eval.c:1636 #27 0x19c73 in Fbyte_code (bytestr=1613019924, vector=-2145076340, maxdepth=4) at bytecode.c:576 #28 0x4e6f3 in funcall_lambda (fun=539278836, nargs=0, arg_vector=0xefbfd09c) at eval.c:3597 #29 0x4d691 in funcall_recording_as (recorded_as=-1607060348, nargs=0, args=0xefbfd098) at eval.c:3214 #30 0x4d785 in Ffuncall (nargs=1, args=0xefbfd098) at eval.c:3238 #31 0x198a6 in Fbyte_code (bytestr=1613018836, vector=-2145077436, maxdepth=4) at bytecode.c:416 #32 0x4e6f3 in funcall_lambda (fun=539277320, nargs=0, arg_vector=0xefbfd460) at eval.c:3597 #33 0x4d691 in funcall_recording_as (recorded_as=-1607060516, nargs=0, args=0xefbfd45c) at eval.c:3214 #34 0x4d785 in Ffuncall (nargs=1, args=0xefbfd45c) at eval.c:3238 #35 0x198a6 in Fbyte_code (bytestr=1613016916, vector=-2145079288, maxdepth=6) at bytecode.c:416 #36 0x4e6f3 in funcall_lambda (fun=539275724, nargs=0, arg_vector=0xefbfd518) at eval.c:3597 #37 0x4df72 in apply_lambda (fun=539275724, numargs=0, unevalled_args=-1607671804) at eval.c:3501 #38 0x4cfeb in Feval (form=1076952004) at eval.c:3085 #39 0x4a568 in condition_case_1 (handlers=-1607671708, bfun=0x4c434 <Feval>, barg=1076952004, hfun=0x23754 <cmd_error>, harg=-1607671804) at eval.c:1653 #40 0x2493d in top_level_1 (dummy=-1607671804) at cmdloop.c:206 #41 0x4a388 in internal_catch (tag=-1607594132, func=0x24914 <top_level_1>, arg=-1607671804, threw=0x0) at eval.c:1328 #42 0x23901 in initial_command_loop (load_me=-1607671804) at cmdloop.c:285 #43 0x45969 in xemacs_21_0_b60_i386_unknown_freebsd2_2_6 (argc=1, argv=0xefbfd80c, envp=0xefbfd814, restart=0) at emacs.c:1705 #44 0x46322 in main (argc=1, argv=0xefbfd80c, envp=0xefbfd814) at emacs.c:2122 uname -a: FreeBSD phaedrus.cmb.net 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Wed Mar 25 02:28:49 GMT 1998 jkh＠time.cdrom.com:/usr/src/sys/compile/GENERIC i386 ./configure '--prefix=/home/rcoleman/beta' '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' XEmacs 21.0-b60 "Poitou60" configured for `i386-unknown-freebsd2.2.6'. Where should the build process find the source code? /home/rcoleman/xemacs/xemacs-21.0.60 What installation prefix should install use? /home/rcoleman/beta What operating system and machine description files should XEmacs use? `s/freebsd.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch 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/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Additional header files: /usr/local/include Additional libraries: /usr/local/lib Runtime library search path: /usr/local/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 native sound support. Compiling in support for Berkeley DB. 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 "flock" for locking mail spool files. 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: ---------------------------------------------------------

3 participants
3 comments

making MINIMAL-TAGBITS the default 25 years, 3 months

Richard Coleman

I thought the plan was to eventually make MINIMAL-TAGBITS on by default. If so, then maybe we should go ahead and make this the default for 21.2.x, so any remaining bugs can be shaken out. -- Richard Coleman coleman(a)math.gatech.edu

1 participants
0 comments

XEmacs 21.0.61 "Poitou61" is released 25 years, 3 months

SL Baur

Available from the usual places: ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.0/ CVS sources are at http://cvs.xemacs.org/ Installable Lisp packages are in: ftp://ftp.xemacs.org/pub/xemacs/packages Thanks to Andy Piper for patch integration. This is pretty much it. Whatever is still broken will pretty much need to get fixed in 21.1. I cannot reproduce the lack of display-time crash reported by Richard Coleman. I don't know whether that's good or bad. I plan on making a final set of tarballs next weekend some time as there is some documentation that needs tweaking. I'm fairly busy getting ready to leave for Japan so I doubt I'll be able to do much. Maybe I can just not sleep for a week ... to 21.0 "Poitou61" -- mswindows modeline crash fix from Jonathan Harris -- picon glyph fix from Gunnar Evermann -- ldap fixes from Oscar Figueiredo -- mswindows accelerator fix from Jonathan Harris -- package fixes from Jan Vroonhof -- configure fixes from Martin Buchholz -- mule xemacs crash fixed -- sound doc cleanup from Charles Waldman -- package admin fixes under mswindows from Charles Waldman -- sound.el name change sync from Andy Piper

2 participants
2 comments

Re: ESD and XEmacs? 25 years, 3 months

SL Baur

Rebecca Ore <rebecca.ore(a)op.net> writes in xemacs-beta(a)xemacs.org: > I thought someone posted here about a trial package to make ESD work > with XEmacs -- going back over the mail, I'd either deleted it as part > of a thread or it's actually posted to the Gnome mailing list. > If someone posted it here, could you repost it as a subject header? I'd > be very happy to test this for you. Not that I'm aware of. XEmacs isn't compatible with GNOME, use KDE.

2 participants
1 comments

Re: mega-package rather than sumo tarball 25 years, 3 months

Jan Vroonhof

Richard Coleman <coleman(a)math.gatech.edu> writes: > I was thinking that when 21.0 is released, it might be better to have a > mega-package (union of all common binary packages) rather than a sumo > tarball. I thought the SUMO tarball was exactly that? Jan

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