June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: anyone successfully built b41 on digital unix 4.0b ? 26 years, 2 months

SL Baur

Reggie Perry pointed out a serious bug in unexalpha.c that got introduced a few betas ago -- a call to bcopy got converted to memcpy without the parameters being reversed. The following patch is in b42 (which will be released shortly). 1998-06-01 SL Baur <steve(a)altair.xemacs.org> * unexalpha.c (unexec): Reverse parameters in call to memcpy. Suggested by Reggie Perry <perry(a)zso.dec.com> Index: src/unexalpha.c =================================================================== RCS file: /usr/local/xemacs/xemacs-20.0/src/unexalpha.c,v retrieving revision 1.4 diff -u -r1.4 unexalpha.c --- src/unexalpha.c 1998/05/06 09:46:51 1.4 +++ src/unexalpha.c 1998/06/02 00:43:38 ＠＠ -302,7 +302,7 ＠＠ * Construct new symbol table header */ - memcpy (oldptr + nhdr.fhdr.f_symptr, buffer, cbHDRR); + memcpy (buffer, oldptr + nhdr.fhdr.f_symptr, cbHDRR); #define symhdr ((pHDRR)buffer) newsyms = nhdr.aout.tsize + nhdr.aout.dsize; ＠＠ -394,7 +394,7 ＠＠ if (!strcmp(s,"_edata")) { found++; - memcpy (x, &n_edata, cbEXTR); + memcpy (&n_edata, x, cbEXTR); n_edata.asym.value = Brk; SEEK (new, newsyms + cbHDRR + i, "seeking to symbol _edata in %s", new_name); ＠＠ -404,7 +404,7 ＠＠ else if (!strcmp(s,"_end")) { found++; - memcpy (x, &n_end, cbEXTR); + memcpy (&n_end, x, cbEXTR); n_end.asym.value = Brk; SEEK (new, newsyms + cbHDRR + i, "seeking to symbol _end in %s", new_name);

2 participants
1 comments

anyone successfully built b41 on digital unix 4.0b ? 26 years, 2 months

Andrew J Cosgriff

Hi all, i've been way out of the loop for a month or two (apologies !), but i've come back and gave b41 a whirl, to find the following : [ ... ] range table storage: 64 lcrecord lists used: 13 lcrecord list storage: 624 font instances used: 1 font instance storage: 64 color instances used: 1 color instance storage: 48 weak lists used: 385 weak list storage: 18480 specifiers used: 385 specifier storage: 47537 glyphs used: 18 glyph storage: 1440 opaques used: 6 opaque storage: 796 opaque lists used: 2 opaque list storage: 96 vectors used: 810 vector storage: 579248 hashtables used: 389 hashtable storage: 31120 /bin/sh: 26567 Memory fault - core dumped I remember mention of default stacksize (limit stacksize in zsh) being too small on DU, so I upped it from 2MB to 8MB, did an rm src/xemacs ; make but still see the same problem... a "where" on the core dump from temacs sez : (gdb) where #0 0x3ff800d23ec in memcpy () #1 0x1200bb61c in unexec ( new_name=0x11fffd7d0 "/net/local/src/build/ajc/xemacs-20/src/xemacs", a_name=0x454000 <Address 0x454000 out of bounds>, data_start=5370646496, entry_address=5005312) at unexalpha.c:305 #2 0x1200a46ac in Fdump_emacs (intoname=5372153456, symname=5372153504) at emacs.c:2489 #3 0x1200ac62c in Feval (form=5373404400) at eval.c:3201 #4 0x1200a70e0 in Fprogn (args=5373255576) at eval.c:829 #5 0x1200ac340 in Feval (form=5373255600) at eval.c:3093 #6 0x1200a6e90 in Fif (args=5373251584) at eval.c:812 #7 0x1200ac340 in Feval (form=5373251608) at eval.c:3093 #8 0x1200ac7e8 in Feval (form=5373289824) at eval.c:3189 #9 0x120166db0 in readevalloop (readcharfun=5371665408, sourcename=5371659264, evalfun=0x1200abc68 <Feval>) at lread.c:1565 #10 0x120165714 in Fload_internal (file=5371659264, no_error=100, nomessage=5370842552, nosuffix=5370831392, codesys=6, used_codesys=5371088904) at lread.c:977 #11 0x1200ac6b4 in Feval (form=5371657528) at eval.c:3217 #12 0x1200a8ce0 in condition_case_1 (handlers=128, bfun=0x1200abc68 <Feval>, barg=5371657528, hfun=0x11fffe660, harg=5371088904) at eval.c:1809 #13 0x12007dd88 in top_level_1 () at cmdloop.c:305 #14 0x1200a87a8 in internal_catch (tag=4603904, func=0x12007dd40 <top_level_1>, arg=5371088904, threw=0x0) at eval.c:1639 #15 0x12007df20 in initial_command_loop (load_me=4831819680) at cmdloop.c:338 #16 0x1200a346c in xemacs_21_0_b41_alpha_dec_osf4_0 (argv=0x11fffee10) at emacs.c:1817 #17 0x1200a3f0c in main (argc=4603904, argv=0x11fffb7a0, envp=0x0) at emacs.c:2180 Any ideas ? (is there any more useful info I can provide ?) Installation file : uname -a: OSF1 goaway.cc.monash.edu.au V4.0 564 alpha alpha ./configure '--with-gcc=no' '--cflags=-O -g3' '--error-checking=all' '--debug=yes' '--gung-ho' '--with-mule' '--with-xfs' '--with-ldap' '--site-includes=/usr/local/include /net/users/ajc/test/giflib/include /net/users/ajc/test/nas/usr/include /net/local/include' '--site-libraries=/usr/local/lib /net/users/ajc/test/giflib/lib /net/users/ajc/test/nas/usr/lib /net/local/lib' '--with-xim=no' '--with-cde=no' '--with-tooltalk=no' '--x-includes=/usr/include' '--x-libraries=/usr/lib' '--with-session=yes' '--with-sound=nas' '--package-path=~/.xemacs::/net/users/ajc/lib/elisp/packages:/usr/local/lib/xemacs/packages' XEmacs 21.0-b41 "San Clemente" configured for `alpha-dec-osf4.0'. Where should the build process find the source code? /net/users/ajc/build/xemacs-20 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/decosf4-0.h' and `m/alpha.h' What compiler should XEmacs be built with? cc -O -g3 Should XEmacs use the GNU version of malloc? no (The GNU allocators don't work with this system configuration). 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 /usr/include Where do we find X Windows libraries? /usr/dt/lib /usr/lib Additional header files: /usr/local/include /net/users/ajc/test/giflib/include /net/users/ajc/test/nas/usr/include /net/local/include Additional libraries: /usr/local/lib /net/users/ajc/test/giflib/lib /net/users/ajc/test/nas/usr/lib /net/local/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in network sound (NAS) support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for LDAP (UMich libs). Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Using XFontSet to provide bilingual menubar. Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "flock" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. 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: ---------------------------------------------------------

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 26 years, 2 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: >> Hrvoje Niksic <hniksic(a)srce.hr> writes: >> >> > > The anology doesn't work as the loadpaths are computed before >> > > .emacs/init.el is loaded. >> > >> > The analogy definitely works. `.cshrc' is a special file, and can't >> > be placed just anywhere. It's not just a random executable. The same >> > goes for .emacs & friends. >> >> No it doesn't... The reason .cshrc is a special file in a special >> location is because there is no user dependent path setup in csh at >> the time it gets loaded. > No, that's not the reason, as I see it. The reason is that .cshrc is > not *supposed* to be loaded from a random PATH location, ever. It's potentially very dangerous to pull init files from miscellaneous places. Has anyone else ever planted trojan .exrc files around to catch^H^H^H^H^Heducate unwary vi users? :-) $ cat .exrc :!kill -11 $PPID

1 participants
0 comments

[patch] src/Makefile.in.in for external widget 26 years, 2 months

Colin Rafferty

Hi- External widget works, but Makefile.in.in does not. There is a function-style #define for EXTW_LINK, that does not get expanded at all. Anyway, here is the patch. Please let this be included for 21.0.

1 participants
0 comments

Beta42 "Somali" is coming today 26 years, 2 months

SL Baur

The core has all outstanding patches applied that are going to be applied and I'm working on getting the Lisp packages updated. There are a lot of patches on the Lisp package queue so it's going to take some time. This is intended to be the final 21.0 beta, so I'm not rushing it.

1 participants
0 comments

add pdb.el to debug package? 26 years, 2 months

Charles G Waldman

I asked several months ago about the possibility of adding the python debugger (pdb.el) to the debug package. As I recall the consensus was "OK, if the author agrees", and the author ; Wolfgang Weitz <wwe(a)aifb.uni-karlsruhe.de> said OK as well.... so, is there still any chance of getting this added to the debug package? The file itself can be found at: ftp://ftp.aifb.uni-karlsruhe.de/pub/wwe/pdb.el

1 participants
0 comments

redundant dir entries for Standards and Texinfo 26 years, 2 months

Christian Nybø

from man/standards.texi, line 12: * Standards: (standards). GNU coding standards. Wouldn't the following line suffice? * Standards: GNU coding standards. The same applies for man/texinfo.texi, line 31. Is there a reason for adding the node name in parentheses as long as it only differs in case? -- chr

1 participants
0 comments

[offtopic] scripting X events? 26 years, 2 months

Greg Klanderman

Sorry for the offtopic noise but I seem to recall one of you once mentioning a free package that allows one to script X events. We have a program with only a gui interface we'd like to run many times as a batch job. I've searched thru my xemacs-beta archives and some X newsgroups and FAQs but it's all "How do I change my background"... Anyway, if someone knows something I'd greatly appreciate it. many thanks greg

2 participants
1 comments

Re: QNX port problems 26 years, 2 months

SL Baur

Sean MacLennan <bn932(a)freenet.carleton.ca> writes: ... > I am trying to port XEmacs to QNX and have hit a snag. I am hoping > someone will immediately see the problem....... > Here is the make output (beta40): > EMACSBOOTSTRAPLOADPATH="/home/xemacs/xemacs-20.0/src/../lisp/:/home/xemacs/xemacs-20.0" > ./temacs -batch -l /home/xemacs/xemacs-20.0/src/../lisp/update-elc.el > Loading /home/xemacs/xemacs-20.0/src/../lisp/update-elc.el... > Loading find-paths.el... (10184) > Loading packages.el... (17300) > Loading setup-paths.el... (4096) > Loading dump-paths.el... (0) > Loading /home/xemacs/xemacs-20.0/src/../lisp/dumped-lisp.el...(160) > EMACSBOOTSTRAPLOADPATH="/home/xemacs/xemacs-20.0/src/../lisp/:/home/xemacs/xemacs-20.0" > ./temacs -batch -l /home/xemacs/xemacs-20.0/src/../lisp/loadup.el dump > Loading /home/xemacs/xemacs-20.0/src/../lisp/loadup.el... > Using load-path (/home/xemacs/xemacs-20.0/src/../lisp/ > /home/xemacs/xemacs-20.0) > Loading /home/xemacs/xemacs-20.0/src/../lisp/dumped-lisp.el...(204) > Loading /home/xemacs/xemacs-20.0/lisp/backquote.elc... (2486) > Loading /home/xemacs/xemacs-20.0/lisp/bytecomp-runtime.elc...Fatal > error: assertion failed, file alloc.c, line 3831, (((EMACS_UINT) ((void > *) (((ptr->car) & ((1UL << ((4 * 8) - 4)) - 1UL))))) & 3) == 0 > make: [xemacs] Error 134 (ignored) > make: *** [xemacs] Error 1 > If it is any help, here are the bytecomp-runtime.el[c], the config.h and > the makefile. Do not hesitate to ask for more info!!!! Um, at least in my case, none of your attachments are very useful for identifying a problem. Please just send the Installation file generated by configure (M-x describe-installation). The code above is one place where the pointer tag bits are being diddled with. You are apparently using the system malloc (using the old GNU Malloc distributed with XEmacs might be easier and it might not). Have you tried building with -DUSE_MINIMAL_TAGBITS? The System malloc on Linux (the new GNU malloc) has a tendency to return pointers which can collide with the usual Lisp tagbits. Check the documentation for malloc and make sure that it does not use mmap. If it does, you will have to arrange to have it turned off while XEmacs is dumping or you will lose. See the code guarded by `#ifdef DOUG_LEA_MALLOC' for clues on how to do this with one implementation.

2 participants
1 comments

Patch for int/string problem in footnote.el 26 years, 2 months

Samuel Mikes

`concat' is called with integer arguments when a footnote is inserted prior to an existing footnote. This patch uses `Footnote-index-to-string' (instead of the %d format) for prettiness value. --- xemacs/packages/lisp/footnote/footnote.el~ Mon Jan 26 05:12:34 1998 +++ xemacs/packages/lisp/footnote/footnote.el Sun May 31 21:50:06 1998 ＠＠ -4,7 +4,7 ＠＠ ;; Author: Steven L Baur <steve(a)altair.xemacs.org> ;; Keywords: mail, news -;; Version: 0.18 +;; Version: 0.19 ;; This file is part of XEmacs. ＠＠ -39,6 +39,8 ＠＠ ;;; Change Log: +;; May-31-1998: In `Footnote-make-hole', `concat' was called with integer +;; argument; now use `Footnote-index-to-string' and `format' ;; Apr-04-1997: Added option to narrow buffer when editing the text of ;; a footnote. ;; Insertion and renumbering now works. ＠＠ -551,8 +553,10 ＠＠ (unless rc (setq rc (car alist-ptr))) (save-excursion - (message (concat "Renumbering from " - (car alist-ptr) " to " (1+ (car alist-ptr)))) + (message (format "Renumbering from %s to %s" + (Footnote-index-to-string (car alist-ptr)) + (Footnote-index-to-string + (1+ (car alist-ptr))))) (Footnote-renumber (car alist-ptr) (1+ (car alist-ptr)) alist-ptr -- Sam Mikes smikes(a)alumni.hmc.edu

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 1998