May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: change to `concat' breaks start-itimer [Was: Problems with gnus and beta40?] 26 years, 6 months

Glynn Clements

Stefanie Teufel wrote: > > > The problem is in your .gnus file. Check it carefully for usage of > > > `concat' and an integer. > > > > No, I had a similar problem due to the use of start-itimer by > > lazy-shot. > > > > I think that the following patch should fix it. > > No, unfortunately. But I know for sure now, that my problem is related > to the beta40, because after installing the beta39 again, everything > seems to be allright. Hmm. Well, the problem is definitely specific to b40. The behaviour of the `concat' function was changed in b40. It no longer accepts integers as arguments, hence the Wrong type argument: sequencep, 2 error. The patch to start-itimer is definitely necessary. However, the change may well have broken other things. Try setting debug-on-error to t. That should give you a backtrace which indicates which function the error is in. -- Glynn Clements <glynn(a)sensei.co.uk>

1 participants
0 comments

Re: Problems with gnus and beta40? 26 years, 6 months

SL Baur

Stefanie Teufel <s.teufel(a)ndh.net> writes: > Hello everybody, > after applying the b40-patch without any problems, I encounter now problems > with gnus. I've changed absolutly nothing in my settings, got the > new version of the xemacs-base-package as recommended, but gnus > complains: > Signaling: (error "Error in ~/.gnus: (wrong-type-argument sequencep > 2)") The problem is in your .gnus file. Check it carefully for usage of `concat' and an integer.

2 participants
1 comments

Re: [failure] XEmacs 21.0-b40 on FreeBSD 2.2.6 26 years, 6 months

SAKIYAMA Nobuo

>>>>> In <m2hg2ptf24.fsf(a)altair.xemacs.org> >>>>> SL Baur <steve(a)xemacs.org> wrote: > > In cl-float-limits, > > 1998-05-10 Hrvoje Niksic <hniksic(a)srce.hr> > > * cl-extra.el (cl-float-limits): Removed; move code to top-level. > All right, why is a Lisp change causing a core dump? Until 21.0-b39, 'cl-float-limits' is *not* executed in temacs. When executing cl-float-limits in dumped xemacs, overflow errors and underflow errors are guarded by (condition-case err body (arith-error nil)) style. But in temacs, signal handlers are not defined as in my previous article. Thus, all overflow errors and underflow errors may cause unguarded SIGFPEs and temacs dumps core. -- SAKIYAMA Nobuo nobuo(a)db3.so-net.or.jp

1 participants
0 comments

Re: [failure] XEmacs 21.0-b40 on FreeBSD 2.2.6 26 years, 6 months

SL Baur

SAKIYAMA Nobuo <nobuo(a)db3.so-net.or.jp> writes: > Loading cl.el... > Loading cl-extra.el...Floating point exception - core dumped > *** Error code 136 ... > This seems to be the same problem as of > <199805120211.LAA11075(a)jjctsn10.pnc.go.jp> '[Failure] b40-pre1 on Alpha/Linux'. > In cl-float-limits, > 1998-05-10 Hrvoje Niksic <hniksic(a)srce.hr> > * cl-extra.el (cl-float-limits): Removed; move code to top-level. All right, why is a Lisp change causing a core dump? This is, of course, a bug that needs to get fixed as soon as possible.

1 participants
0 comments

[failure] XEmacs 21.0-b40 on FreeBSD 2.2.6 26 years, 6 months

SAKIYAMA Nobuo

I cannot build 21.0-b40 on FreeBSD 2.2.6 RELEASE. abbreviated log is like this. % uname -m -s -r FreeBSD 2.2.6-RELEASE i386 % make [......] EMACSBOOTSTRAPLOADPATH="/usr3/src/xemacs-21.0-b40/src/../lisp/:/usr3/src/xemacs-21.0-b40" ./temacs -batch -l /usr3/src/xemacs-21.0-b40/src/../lisp/update-elc.el Loading /usr3/src/xemacs-21.0-b40/src/../lisp/update-elc.el... [......] Loading cl.el... Loading cl-extra.el...Floating point exception - core dumped *** Error code 136 Stop. *** Error code 1 Stop. This seems to be the same problem as of <199805120211.LAA11075(a)jjctsn10.pnc.go.jp> '[Failure] b40-pre1 on Alpha/Linux'. In cl-float-limits, 1998-05-10 Hrvoje Niksic <hniksic(a)srce.hr> * cl-extra.el (cl-float-limits): Removed; move code to top-level. The code in ex. cl-float-limits causes 'Floating point exception' in some systems. This exception is normally caught by arith_error (in data.c). But when temacs executes update-elc.el in batch-mode, SIGFPE is not caught. See the following function in src/data.c. void init_data_very_early (void) { /* Don't do this if just dumping out. We don't want to call `signal' in this case so that we don't have trouble with dumping signal-delivering routines in an inconsistent state. */ #ifndef CANNOT_DUMP if (!initialized) return; #endif /* CANNOT_DUMP */ signal (SIGFPE, arith_error); #ifdef uts signal (SIGEMT, arith_error); #endif /* uts */ } -- SAKIYAMA Nobuo nobuo(a)db3.so-net.or.jp

1 participants
0 comments

Re: is `-name' functional? 26 years, 6 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > I would expect `xemacs -name fubar' to start a resourceless XEmacs Has this ever worked? I don't recall it ever working. If the argument given to -name has valid resources they will be used, but I've never gotten a resourceless XEmacs this way, I've had to use `xrdb < /dev/null'.

2 participants
1 comments

add-little-package.sh 26 years, 6 months

Jason R Mastaler

A `make install' of b40 failed for me until I manually added "add-little-package.sh" from the 20.4 distribution. ==== Installing utilities run internally by XEmacs. ./make-path /home/jason/wk/XEMACS/beta/v21/lib/xemacs-21.0-b40/i386-pc-solaris2.5.1 if test "`(cd /home/jason/wk/XEMACS/beta/v21/lib/xemacs-21.0-b40/i386-pc-solaris2.5.1 && /bin/pwd)`" != "`/bin/pwd`"; then \ for f in make-path wakeup profile make-docfile digest-doc sorted-doc movemail cvtmail fakemail yow hexl gnuserv mmencode; do \ (cd .. && /usr/local/bin/install -c lib-src/$f /home/jason/wk/XEMACS/beta/v21/lib/xemacs-21.0-b40/i386-pc-solaris2.5.1/$f) ; \ done ; \ fi if test "`(cd /home/jason/wk/XEMACS/beta/v21/lib/xemacs-21.0-b40/i386-pc-solaris2.5.1 && /bin/pwd)`" \ != "`(cd /usr/local/SourceTrees/xemacs-21.0-b40/lib-src && /bin/pwd)`"; then \ for f in rcs2log vcdiff gzip-el.sh install-sid send-pr tm-au tm-file tm-html tm-image tm-mpeg tm-plain tm-ps tmdecode add-little-package.sh add-big-package.sh; do \ (cd .. && /usr/local/bin/install -c /usr/local/SourceTrees/xemacs-21.0-b40/lib-src/$f /home/jason/wk/XEMACS/beta/v21/lib/xemacs-21.0-b40/i386-pc-solaris2.5.1/$f); \ done ; \ fi /usr/local/bin/install: /usr/local/SourceTrees/xemacs-21.0-b40/lib-src/add-little-package.sh: No such file or directory *** Error code 1 make: Fatal error: Command failed for target `/home/jason/wk/XEMACS/beta/v21/lib/xemacs-21.0-b40/i386-pc-solaris2.5.1' ====

1 participants
0 comments

Vertical Divider 26 years, 6 months

Glynn Clements

I've just built b40, and now I've got this vertical divider thingy wasting valuable screen real-estate. A couple of questions: a) is there a way to disable it completely? Using (set-specifier vertical-divider-spacing 0 'global) (set-specifier vertical-divider-line-width 0 'global) still leaves vestiges of it. b) If not, can the dimensions be controlled by X resources? -- Glynn Clements <glynn(a)sensei.co.uk>

2 participants
1 comments

Re: gnu malloc vs. system malloc on OpenBSD 26 years, 6 months

SL Baur

Hans Guenter Weigand <hgweigand(a)wiesbaden.netsurf.de> writes: ... >> It took a great deal of fiddling to use the system malloc (the newest >> GNU malloc) on Linux. Have you tried setting -DUSE_MINIMAL_TAGBITS? >> This moves the Lisp tag bits somewhere where they won't step on the >> high bits of pointers. > It is building at the moment. Expect the result tomorrow, I'm too > tired to wait for it to complete. The other bit of fiddling, as Olivier pointed out, was to unconditionally disable mmap while XEmacs dumps since this is a guaranteed lose. You can grep for `DOUG_LEA_MALLOC' to see which changes were made for this. Good luck.

1 participants
0 comments

[Patch] Re: OpenBSD support for XEmacs 21.0b40 26 years, 6 months

Hans-Guenter Weigand

>From: Olivier Galibert, galibert(a)pobox.com >On Sat, May 16, 1998 at 09:44:14PM +0200, Hans Guenter Weigand wrote: >> As promised last week I made my patches against the most recent sources. > >Your patch has been broken by folding. F.i.: > >> -#if ! defined (__NetBSD__) && ! defined (__linux__) >> +#if ! defined (__NetBSD__) && ! defined (__linux__) && !defined >> (__OpenBSD__) > >Could you send it again as an attachment please ? Yes, of course. I am sorry, this is an easy-to-use mailer, but not very intelligent... -hgw

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 May 1998