January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Steve's tty problem -- attention Linux testers building with gpm 26 years

SL Baur

The crash I'm getting is occurring in a call to Gpm_Open, but only when XEmacs is run inside an xterm. When run on the Linux console the splash screen comes up. When I build without GPM everything is fine. I'm not done poking around to get more information, but if everyone with access to a Linux machine for testing could do some checking of this it would be helpful. In particular it would be good to know if this is only a glibc-2.0.1xx problem, or something else specific to my development environment, or if it's Mule -vs- no-Mule, etc. Thanks for any info. $ gdb src/xemacs GNU gdb 4.16.85 Copyright 1997 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 "i586-pc-linux-gnu"... (gdb) run -nw Starting program: /devel/xemacs/build20/mule/src/xemacs -nw Program received signal SIGSEGV, Segmentation fault. 0x403bd051 in _IO_fflush (fp=0x40451100) at iofflush.c:41 41 result = _IO_SYNC (fp) ? EOF : 0; (gdb) where #0 0x403bd051 in _IO_fflush (fp=0x40451100) at iofflush.c:41 #1 0x402da5cd in Gpm_Open () #2 0xd0000 in ?? () Cannot access memory at address 0x1000d. (gdb) quit The configuration I'm testing is Linux 2.2.0-pre4/2.2.0-pre5-ac1, glibc-2.0.108 and glibc-2.0.109, pgcc/egcs-1.1.1, XFree86-3.3.3 and gpm-1.13. uname -a: Linux demeter.xemacs.org 2.2.0-pre5-ac1 #2 SMP Thu Jan 7 02:53:22 PST 1999 i686 unknown /devel/xemacs/xemacs-21.0/configure '--cflags=-g' '--with-mule=yes' '--with-dialogs=athena3d' '--with-scrollbars=athena3d' '--use-union-type=yes' '--with-xim=xlib' '--with-xfs' '--mail-locking=file' '--extra-verbose=no' '--srcdir=/devel/xemacs/xemacs-21.0' '--with-gnu-make' '--with-gpm=no' XEmacs 21.0-b62 "Pyrenean" configured for `i686-pc-linux'. Where should the build process find the source code? /devel/xemacs/xemacs-21.0 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 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 ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for proper session-management. Using Lucid menubars. Using Athena-3d scrollbars. Using Athena-3d 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. 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: ---------------------------------------------------------

2 participants
1 comments

What to Dl to compile beta 26 years

David Kropman

Hi What do I have to download to compile a beta? I seem to have read quite a few documents but have not found out exactly what to dl. Here is a list of things that I have dl'ed: Xemacs-21.0.60.tar.gz Xemacs-21.0.60-elc.tar.gz Xemacs-21.0.60-info.tar.gz xemacs-base-1.27-pkg.tar.gz Also a few extra libs from aux But my big question is what do I do with the packages xemacs-base-1.27-pkg.tar.gz and the others that I have downloaded like cc-mode etc? Do I need them before I run configure/make? Where do I put them? On the web site you mention the following: XEmacs 20.3-beta15 a number of lisp packages aredistributed separately of the main distribution. Please see the directory ftp://ftp.xemacs.org/pub/xemacs/beta/packages-20.3/, read theinstructions in etc/BETA But I cannot find the dir. Many Thanks -- ****************************************************************************** The use of the Truworths e-mail facility is not permitted for the distribution of chain letters or offensive email of any nature whatsoever. Truworths hereby distances itself from and accepts no liability in respect of the unauthorised use of its e-mail facility or the sending of e-mail communications for other than strictly business purposes. Truworths furthermore disclaims liability for any unauthorised instruction for which permission was not granted. Any recipient of an unacceptable communication, a chain letter or offensive material of any nature is requested to report it to abuse(a)truworths.co.za

2 participants
1 comments

Re: 21.2-b8 SEGV during garbage collection 26 years

Didier Verna

Karl Kleinpaste writes: Karl> Program received signal SIGSEGV, Segmentation fault. 0x808198c in Karl> #3 0x80ac439 in Ffuncall (nargs=3, args=0xbfffe80c) at eval.c:3135 Karl> #4 0x80882f8 in execute_optimized_program ( ... (gdb) list 4112 { 4113 One more indice of the (decidedly very probable) bug introduced in the latest byte compiler mega-patch. One more because the ones I got recently, along with the doctor-crash someone reported earlier look very very similar. -- / / _ _ 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

21.2-b8 SEGV during garbage collection 26 years

Karl Kleinpaste

In my XEmacs which spends most of its time running Gnus, I just got this failure: (gdb) r Starting program: /usr/local/bin/xemacs-21.2-b8 -geometry 207x89+1282+0 -f gnus-init Program received signal SIGSEGV, Segmentation fault. 0x808198c in marked_p (obj=153503600) at alloc.c:4117 4117 return PURIFIED (lheader) || MARKED_RECORD_HEADER_P (lheader); (gdb) bt #0 0x808198c in marked_p (obj=153503600) at alloc.c:4117 #1 0x80a5539 in finish_marking_weak_hash_tables ( obj_marked_p=0x8081970 <marked_p>, markobj=0x807eca4 <mark_object>) at elhash.c:1178 #2 0x80803f7 in garbage_collect_1 () at alloc.c:4477 #3 0x80ac439 in Ffuncall (nargs=3, args=0xbfffe80c) at eval.c:3135 #4 0x80882f8 in execute_optimized_program ( ... (gdb) list 4112 { 4113 struct lrecord_header *lheader = XRECORD_LHEADER (obj); 4114 #if defined (ERROR_CHECK_GC) && defined (USE_INDEXED_LRECORD_IMPLEMENTATION) 4115 assert (lheader->type <= last_lrecord_type_index_assigned); 4116 #endif 4117 return PURIFIED (lheader) || MARKED_RECORD_HEADER_P (lheader); 4118 } 4119 #ifndef LRECORD_STRING 4120 case Lisp_Type_String: 4121 { (gdb) p lheader No symbol "lheader" in current context. (gdb) p obj $13 = -1 (gdb) up #1 0x80a5539 in finish_marking_weak_hash_tables ( obj_marked_p=0x8081970 <marked_p>, markobj=0x807eca4 <mark_object>) at elhash.c:1178 1178 if (obj_marked_p (e->value)) (gdb) list 1173 break; 1174 1175 case HASH_TABLE_VALUE_WEAK: 1176 for (; e < sentinel; e++) 1177 if (!HENTRY_CLEAR_P (e)) 1178 if (obj_marked_p (e->value)) 1179 MARK_OBJ (e->key); 1180 break; 1181 1182 case HASH_TABLE_KEY_CAR_WEAK: (gdb) p e $14 = (hentry *) 0x82df958 (gdb) p e->value $15 = 153503600 uname -a: Linux beaver.jprc.com 2.1.131 #5 SMP Thu Dec 17 16:46:02 EST 1998 i686 unknown ./configure '--with-pop' '--with-mule' '--with-png' '--error-checking=none' '--debug=no' XEmacs 21.2-b8 "Artemis" configured for `i686-pc-linux'. Where should the build process find the source code? /home/karl/src/x/xemacs-21/xemacs-21.2.8 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 raw Xlib to provide XIM support. 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 POP for mail access. Using Lisp_Objects with minimal tagbits.

1 participants
0 comments

Re: What to Dl to compile beta 26 years

Didier Verna

David Kropman writes: David> But my big question is what do I do with the packages David> xemacs-base-1.27-pkg.tar.gz and the others that I have downloaded like David> cc-mode etc? To bootstrap yourselve, install xemacs-base in /usr/local/lib/xemacs/xemacs-packages/. If you want a Mule'ized build, get mule-base and install it in /usr/local/lib/xemacs/mule-packages. The other packages can be installed later. -- / / _ _ 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: 21.0 TTY show-stopper 26 years

SL Baur

Didier Verna <verna(a)inf.enst.fr> writes in xemacs-beta(a)xemacs.org: ... > 21.2 is pretty stable already. I doubt it will take as long to > release 21.2 as it took for 21.0. Probably not, but I hope it will be the version that eliminates dumping and that will take some time to shake down.

2 participants
1 comments

21.0.62: Can't get pui to work 26 years

Holger Schauer

Hi folks ! I just wanted to mess around with the new and updated pui-stuff. This works just fine in my Solaris Poitou b57. But under b62 I just get: Package-get PGP signature failed to verify WARNING: Can't find the right public key-- can't check signature integrity. WARNING: Can't find the right public key-- can't check signature integrity. Verifying... Loading mc-pgp...done Loading mc-pgp... > /anonymous＠ftp.xemacs.org:/pub/xemacs/packages/package-index.LATEST.pgp...done > ＠ftp.xemacs.org:/pub/xemacs/packages/package-index.LATEST.pgp...100% (1.2 KB/s) Please note, that I do have PGP installed, but I don't have the PGP-Signatures installed on the system. I remember having heard about a variable to stop using PGP. So, where it is or what else am I supposed to do (besides fetching the signatures)? Holger -- --- http://www.coling.uni-freiburg.de/~schauer/ --- "Hey sister, have you heard? Some people stand like trees, without a word and what that means is that some people don't talk." -- Violent Femmes, "Never Tell"

1 participants
0 comments

Re: 21.0-b60 Bug in tm 26 years

Raymond Toy

>>>>> "Kyle" == Kyle Jones <kyle_jones(a)wonderworks.com> writes: Kyle> Raymond Toy writes: >> A colleague of mine noticed that in the latest versions of tm (1.15) >> and vm (1.14), there's a small bug. tm-vm uses vm-sprintf, but that >> no longer exists in vm. Can vm-summary-sprintf be used instead? Kyle> Not without some modifications, as the parameter list for Kyle> vm-summary-sprintf is different than vm-sprintf. This will Kyle> probably work: Kyle> (defun vm-sprintf (var msg &optional tok) Kyle> (vm-summary-sprintf (symbol-value var) msg tok)) Thanks! Yup. On a whim, I tried that last night when my wife complained that she couldn't forward mail anymore. Since VM has it's own MIME support, I suppose I can just stop using tm and vm. Question: should tm-vm be fixed so it will use vm-summary-sprintf if vm-sprintf doesn't exist? If so, I'll try to come up with a patch. Ray

1 participants
0 comments

Re: 21.0 TTY show-stopper 26 years

Didier Verna

Rick Campbell writes: Rick> The last release was almost a year ago. If there's even the most remote Rick> chance that the next release could be current for anywhere near as long, Rick> I think that leaving this bug in would be unwise. 21.2 is pretty stable already. I doubt it will take as long to release 21.2 as it took for 21.0. -- / / _ _ 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: 21.0 TTY show-stopper 26 years

SL Baur

Rick Campbell <rick(a)campbellcentral.org> writes in xemacs-beta(a)xemacs.org: > [1 <text/plain; US-ASCII (7bit)>] > Date: Thu, 07 Jan 1999 08:11:00 +0000 > From: Andy Piper <andyp(a)parallax.co.uk> > I see the redisplay thing but I hardly think its a showstopper. > The last release was almost a year ago. If there's even the most > remote chance that the next release could be current for anywhere near > as long, I think that leaving this bug in would be unwise. O.K. I see where you're coming from. There's always that possibility. I am hoping that the way things will work in the next cycle will be that the primary developmental thrust will be towards working on the 21.2 source tree with periodic updates and releases of 21.1.x made as bug fixes and patches come in. Put another way, even if 21.0.63 is released with this display problem, there will be a fix (if someone cares enough to find and fix the problem) released in 21.1.something in a few weeks. One of the smoothest upgrade cycles we had was Shelton-macs 19.16 which had periodic patch kits made and I'm hoping that we can duplicate that in a more formal fashion.

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