December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: failure report: 21.0.60 dies on Xt error 26 years, 5 months

Karl Kleinpaste

Didier Verna <verna(a)inf.enst.fr> writes: > I would suggest that first, you recompile without Motif, and see if > you can still reproduce the bug. Very interesting. I didn't exactly de-install Motif -- I can't do that, as there is other stuff here that requires it -- but I did move its includes and libraries out of visibility for the duration of a reconfiguration and rebuild. The Xt error I mentioned no longer occurs, and I am using 21.0.60 without problem right now. Now I have to wonder if I should go back to trying to run 21.2-bX...

1 participants
0 comments

21.2.5 sucess on AIX 4.3.2 (mostly) 26 years, 5 months

Valdis Kl=?iso8859-4?Q?=BA?=tnieks

Built from fresh tarballs and the patch to bytecode.c. Seems to be working OK. Note the following: 1) Xt event loop *still* broken in AIX 4.3.2. 2) --with-dialogs=athena needed to avoid a crash. 3) --with-dragndrop=no needed to avoid a crash. I still need to double-check if (2) and (3) are still required under 4.3.2, and we'll have to come up with something for the Problems file for (1). I can build a bin-kit statically linked against the X11R6.4 libs that works, but that won't help the people trying to build it themselves. /Valdis uname -a: AIX black-ice 3 4 003260504C00 ./configure '-with-gcc=no' '--compiler=xlc' '--cflags=-O3 -qstrict -qlibansi -qarch=ppc -qtune=604 -qproto' '--with-dragndrop=no' '--with-dialogs=athena' '--gung-ho' '--dynamic=yes' '--debug=no' '--error-checking=none' '--with-mule=no' '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' XEmacs 21.2-b5 "Aphrodite" configured for `powerpc-ibm-aix4.3.2.0'. Where should the build process find the source code? /home/valdis/src/xemacs-21.2.5/src What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/aix4-2.h' and `m/ibmrs6000.h' What compiler should XEmacs be built with? xlc_r -O3 -qstrict -qlibansi -qarch=ppc -qtune=604 -qproto 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/dt/include Where do we find X Windows libraries? /usr/dt/lib Additional header files: /usr/local/include Additional libraries: /usr/local/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 support for GNU DBM. Compiling in support for ToolTalk. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "lockf" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation.

1 participants
0 comments

Re: XEmacs 21.0.60 is released 26 years, 5 months

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes in xemacs-beta(a)xemacs.org: > > > Did my cus-dep bugfix make it to 21.0.60? > > It was labeled hands off -- "Does this patch fix the problem?" It was more of a rhetorical question. :-) When I mail a patch to xemacs-patches, I normally mean it to be applied to XEmacs. I guess I'll have to be more careful about phrasing of the text accompanying a patch.

1 participants
0 comments

Re: XEmacs 21.0.60 is released 26 years, 5 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes in xemacs-beta(a)xemacs.org: > Did my cus-dep bugfix make it to 21.0.60? It was labeled hands off -- "Does this patch fix the problem?" and there was no follow-up to say that it did. I've now applied it to both branches. > I think it should be in 21.0 because it's package-related, and > without it many packages cannot be built properly. O.K.

1 participants
0 comments

Re: XEmacs 21.0.60 is released 26 years, 5 months

Hrvoje Niksic

Kenneth Pĺlsson <kenneth.palsson(a)masystem.se> writes: > I successfully compiled the XEmacs 21.0.60 on AIX 4.3, but when i > tried to run it on a VT220 terminal it didn't respond to pressed > keys. I have read that there is a problem with Emacs on AIX 4.3 (but > it works fine on earlier releases of AIX). Has the problem been > resolved in this distribution? Since you say that you compiled XEmacs 21.0.60 and that the problem persists, is it not obvious that the problem was *not* resolved in this distribution? Can you provide more information, such as trace output that shows if XEmacs is "stuck" in a system call. It might also be useful to run XEmacs with gdb and see where it gets stuck. When you fix the problem, don't forget to send out the patches to <xemacs-patches(a)xemacs.org>. (OK, this last part is optional.:-)

1 participants
0 comments

Re: failure report: 21.0.60 dies on Xt error 26 years, 5 months

Didier Verna

Karl Kleinpaste writes: Karl> This is RedHat 5.1, Linux 2.0.34, assorted XFree RPMs 3.3.2.3-18, and Karl> Motif 2.0.1. I would suggest that first, you recompile without Motif, and see if you can still reproduce the bug. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

RE: XEmacs 21.0.60 is released 26 years, 5 months

Kenneth Pålsson

I successfully compiled the XEmacs 21.0.60 on AIX 4.3, but when i tried to run it on a VT220 terminal it didn't respond to pressed keys. I have read that there is a problem with Emacs on AIX 4.3 (but it works fine on earlier releases of AIX). Has the problem been resolved in this distribution? Kenneth Pålsson MA-system, Lund, SWEDEN >---------- >From: SL Baur[SMTP:steve＠xemacs.org] >Sent: den 11 december 1998 07.01 >To: xemacs-announce(a)xemacs.org >Subject: XEmacs 21.0.60 is released > >Get it from the usual places. > >Tar: > ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.0/ >CVS: > http://cvs.xemacs.org/ >Packages: > ftp://ftp.xemacs.org/pub/xemacs/packages/ > >The SUMO tarballs are up to date. Untar them in $prefix/lib/xemacs. > >This is another experimental release that happened to work. I hope to >release a "real" 21.0 within a few days. All emergency patches I >could find have been applied. If anything has been missed, scream at >me and point me in the direction of the patch I forgot or resend it. > >The only technical detail lacking for release is a working PGP and >we're working on that. > >There will be periodic 21.1 maintenance releases while folks are >developing cool stuff in 21.2. > >Note that until PGP signing is possible on cvs.xemacs.org I'm not >updating the individual binary package tarballs. Sigh. If it's not >one thing, it's another. > > >to 21.0 "Poitou60" >-- help-echo message fix from Hrvoje Niksic >-- Fix building with union type on MS Windows NT from Andy Piper >-- Installation/Installation.el/config.values for MS Windows from Adrian > Aichner >-- Package get cleanups from Greg Klanderman and Jan Vroonhof >-- Avoid defining CLASH_DETECTION on MS Windows NT from Adrian Aichner >-- Package UI fixes from Jan Vroonhof > >to 21.0 "Poitou59" >-- Menu accelerator bug fix from Didier Verna >-- easymenu.el synch with FSF from Jan Vroonhof >-- chartable bug fixes from Hrvoje Niksic >-- Various MULE filenaming/localization bug fixes from Didier Verna >-- Linux/ARM support from James LewisMoss >-- Realpath fix for UnixWare2.1.3 from Takeshi Hagiwara >-- OSS Sound support for AIX from Michael Sperber >-- msw-faces X11 emulation fix from Adrian Aichner >-- Wnn6 detection fix from IENAGA Kazuyuki >-- More Cygwin b20 from Andy Piper >-- 64 bit cleanliness fix from Olivier Galibert >-- Package-get updates from Jan Vroonhof and Greg Klanderman >-- Movemail build fix for MS Windows NT from Andy Piper >-- Clicking on buttons not switching windows patch from Hrvoje Niksic >-- Cygwin b20 support from Andy Piper >-- Autoload cookie fix for cus-face.el from Jan Vroonhof >-- Frame resize inside window fix for MS Windows from Andy Piper >-- Type clean up patches from Steve Carney >-- movemail pop patches from Andy Piper >-- Fix auto-save-directory-fallback hardcoding at dump time from Jan Vroonhof >-- Package loading fixes from Greg Klanderman >-- Package Tool Finishing Touches from Jan Vroonhof >-- package-get-base.el removed from the core >-- BS/DEL fix from Glynn Clements >-- Tty vertical divider width now defaults to 1 instead of 0 >-- MS Windows toolbar fixes from Jonathan Harris >-- Fix for XtDisplay being called with stale widget from Takeshi Hagiwara >-- Fixes for Cygwin b20 from Andy Piper >-- Package UI fetching improvements from Greg Klanderman >-- isearch regexp pruning bugfix from Hrvoje Niksic >-- package deletion fixes from Jan Vroonhof >-- gnuclient fix from Jan Vroonhof >

1 participants
0 comments

failure report: 21.0.60 dies on Xt error 26 years, 5 months

Karl Kleinpaste

(I'm not [yet] an xemacs-beta subscriber; please reply directly if needed.) I can readily induce a SEGV failure when disposing of a 2nd frame, usually having been created via hitting the *Info* button in the toolbar. Generally, the circumstance seems to be related to whether the original buffer from which the 2nd was created was "busy", where "busy" means, *very* roughly, that the original buffer had enough text in it that it had extended below the bottom of the visible buffer space; if the original buffer contains a small file which doesn't extend beyond visible bottom, I don't seem to get this error. (I don't explain it, I just report it.) This particular stack trace was caused by having gotten into *Info*, wandering around the Gnus manual for a while, and then hitting the exit toolbar button in *Info*. The attempt to delete the frame fails. "Installation" is after the trace. This is RedHat 5.1, Linux 2.0.34, assorted XFree RPMs 3.3.2.3-18, and Motif 2.0.1. --karl (gdb) r Starting program: /usr/local/bin/xemacs-21.0-b60 Program received signal SIGSEGV, Segmentation fault. 0x40262d2d in XtIsSubclass () (gdb) bt #0 0x40262d2d in XtIsSubclass () #1 0x40263a36 in XtDisplayOfObject () #2 0x400fd135 in unset_current_xic () #3 0x400fb759 in _XmImFreeShellData () #4 0x40115423 in Destroy () #5 0x40259e36 in Phase2Destroy () #6 0x40259c97 in Recursive () #7 0x4025a16a in XtPhase2Destroy () #8 0x4025a249 in _XtDoPhase2Destroy () #9 0x4025a3c7 in XtDestroyWidget () #10 0x8161ae8 in x_delete_frame (f=0x884a590) at frame-x.c:2651 #11 0x80f7d5f in delete_frame_internal (f=0x884a590, force=0, called_from_delete_device=0, from_io_error=0) at frame.c:1530 #12 0x80f7fa3 in Fdelete_frame (frame=142910864, force=137130132) at frame.c:1676 #13 0x80a802e in Feval (form=142350672) at eval.c:3063 #14 0x80a61f5 in condition_case_3 (bodyform=142350672, var=137130132, handlers=142346884) at eval.c:1653 #15 0x80887af in Fbyte_code (bytestr=140636292, vector=142698928, maxdepth=7) at bytecode.c:576 #16 0x80a9296 in funcall_lambda (fun=139917484, nargs=0, arg_vector=0xbfffef60) at eval.c:3597 #17 0x80a87d5 in funcall_recording_as (recorded_as=139917484, nargs=0, args=0xbfffef5c) at eval.c:3214 #18 0x80a96c2 in apply1 (fn=139917484, arg=137130132) at eval.c:3238 #19 0x80897b7 in Fcall_interactively (function=142684932, record_flag=137130132, keys=137130132) at callint.c:397 #20 0x80a85a7 in funcall_recording_as (recorded_as=137202896, nargs=1, args=0xbffff1f4) at eval.c:3193 #21 0x80a88c1 in Ffuncall (nargs=2, args=0xbffff1f4) at eval.c:3238 #22 0x80883e2 in Fbyte_code (bytestr=136643524, vector=136643672, maxdepth=9) at bytecode.c:416 #23 0x80a9296 in funcall_lambda (fun=136643808, nargs=1, arg_vector=0xbffff31c) at eval.c:3597 #24 0x80a87d5 in funcall_recording_as (recorded_as=138027296, nargs=1, args=0xbffff318) at eval.c:3214 #25 0x80a88c1 in Ffuncall (nargs=2, args=0xbffff318) at eval.c:3238 #26 0x808ac1d in Fcall_interactively (function=138027296, record_flag=137130132, keys=137130132) at callint.c:949 #27 0x80a73a3 in Fcommand_execute (cmd=138027296, record=137130132, keys=137130132) at eval.c:2584 #28 0x80d79b6 in execute_command_event (command_builder=0x83ee148, event=142956256) at event-stream.c:4346 #29 0x80d8082 in Fdispatch_event (event=142956256) at event-stream.c:4685 #30 0x80901ac in Fcommand_loop_1 () at cmdloop.c:579 #31 0x809003a in command_loop_1 (dummy=137130132) at cmdloop.c:494 #32 0x80a5f45 in condition_case_1 (handlers=137130244, bfun=0x8090024 <command_loop_1>, barg=137130132, hfun=0x808fc44 <cmd_error>, harg=137130132) at eval.c:1653 #33 0x8090380 in command_loop_2 (dummy=137130132) at cmdloop.c:256 #34 0x80a5d68 in internal_catch (tag=137204840, func=0x809034c <command_loop_2>, arg=137130132, threw=0x0) at eval.c:1328 #35 0x808fe7e in initial_command_loop (load_me=137130132) at cmdloop.c:305 #36 0x80a345d in xemacs_21_0_b60_i686_pc_linux (argc=1, argv=0xbffff758, envp=0xbffff760, restart=0) at emacs.c:1705 #37 0x80a3b19 in main (argc=1, argv=0xbffff758, envp=0xbffff760) at emacs.c:2122 uname -a: Linux beaver.jprc.com 2.0.34 #1 Tue Jul 21 16:49:33 EDT 1998 i686 unkn own ./configure '--with-pop' '--with-mule' '--with-png' '--error-checking=none' XEmacs 21.0-b60 "Poitou60" configured for `i686-pc-linux'. Where should the build process find the source code? /home/karl/src/x/xemac s-21/xemacs-21.0.60 What installation prefix should install use? /usr/local 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 -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/X11/include Where do we find X Windows libraries? /usr/X11/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 native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using POP for mail access Using Lisp_Objects with minimal tagbits. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage.

1 participants
0 comments

Make that [Success]! (Sorry) 26 years, 5 months

Kevin Oberman

How I manage to screw up something as simple as "Success" vs. "Failure", I don't know. But I managed. My build on DU 4.0D using DECC, gnu make, with CDE, jpeg, libz, and xpm (and a lot of other stuff) was very successful! Sorry for any confusion I might have caused with a body that did not agree with the subject. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634

1 participants
0 comments

[Failure] XEmacs 21.0 "Poitou60" (osf4.0d) 26 years, 5 months

Kevin Oberman

Built 21.0 beta 60 from scratch using the base, elc, and info tarballs. Since this is getting close to release, I'll report the following trivia: cc -c -O3 -std -Demacs -I. -DHAVE_CONFIG_H -std -I/usr/local/include -I/usr/dt/include cmdloop.c cc: Warning: cmdloop.c, line 507: Non-void function "Fcommand_loop_1" does not contain a return statement. DEFUN ("command-loop-1", Fcommand_loop_1, 0, 0, 0, /* ^ Not exactly significant, but I figured I would mention it. I am very concerned about the pgp stuff, though. I don't have a root PGP configuration, so my attempt to update packages from the root account died with a message that "Package-get PGP signature failed to verify". This is not awful, but it may confuse anyone who does not have PGP. I see no reference to PGP in README, INSTALL, or PROBLEMS. A grep -i for pgp found nothing in the top directory. It is important that this be documented up front as well as how to override the PGP requirement for those who don't have PGP. (And many are forbidden to use it.) Just my two bits. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634

1 participants
0 comments

2025

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