May 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [for 21.1.1] Patch for Patchlevels [Was 21.0-b67] 25 years, 6 months

SL Baur

This patch has been committed to the 21.1 branch. Everyone who has been unhappy please test it before I make 21.1.1. I'm not sure I like the way the patch level is put into `emacs-version' -- I want it to appear as X.Y.Z, but I know there hasn't yet been consensus for that change. Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-review(a)xemacs.org: > SL Baur <steve(a)xemacs.org> writes: >> > Charles and I are now on the record as talking you in to it. >> >> Please do not change the version number. If you need a release with a >> non-beta splash screen, it should be numbered 21.1.1 with the >> beta-detection code fixed. > OK, here is the for patch that. This turns emacs_beta_version into a > patch level when emacs_is_beta is not defined. The 21.2.x release > process needs to be fixed to include that, but that is not a priority > right now. > This in a works for me stage. I need to do some real work now. I hope > somebody can take this and make 21.1.1 this weekend.

1 participants
0 comments

Re: Where is makeinfo [Re: build problem with-mule]? 25 years, 6 months

Gunnar Evermann

"T. Kurosaka - Sun Professional Services" <kuro(a)Japan.Sun.COM> writes: > Gunnar, > Thank you for your reply. The core dumping problem is now gone, > thanks to the --gung-ho switch. (What does this do?) ok, but as Hrvoje mentioned this probably just hides the bug. > I have not tried if your recent fix works yet. please do! Preferably do a 'make distclean', apply the patch and then try to rebuild using exactly the configure call that produced the crash before (i.e. without -gung-ho). > My next problem is that build abnormally ends when it couldn't find > makeinfo, as shown bellow. The beta tar file does not seem to > include this command. Am I supposed to download "makeinfo" > individually from somewhere else? yes, makeinfo is part of GNU texinfo. Get it from you nearest GNU mirror. > Because of this I could not finish "make install" either, and > probably because of that, running the resulting xemacs reports lack > of setup-japanese-environment function, or cannot show outline mode. maybe, but I doubt it. running in place should be fine. Have you installed the necessary packages (or the sumo tarball)? Gunnar -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

1 participants
0 comments

21.1 25 years, 6 months

Vin Shelton

What is the tag for release 21.1? The CVS command checkout -rr21-1-1 didn't work, but -r21-1-0 fetched a bunch of stuff. Did I get the right stuff? - vin

1 participants
0 comments

ERROR_CHECK_BYTE_CODE not #defined 25 years, 6 months

Hrvoje Niksic

I noticed that ERROR_CHECK_BYTE_CODE is not defined in my config.h, although I configured with --error-checking=all. I would expect the value of `all' to define all the ERROR_CHECK_* constants. ERROR_CHECK_HASH_TABLE is another one untouched by --error-checking=all. Bug or feature?

1 participants
0 comments

Re: Where is makeinfo [Re: build problem with-mule]? 25 years, 6 months

Hrvoje Niksic

"T. Kurosaka - Sun Professional Services" <kuro(a)Japan.Sun.COM> writes: > Thank you for your reply. The core dumping problem is now gone, > thanks to the --gung-ho switch. (What does this do?) <gory details> It enables the preprocessor switches -DUSE_MINIMAL_TAGBITS and -DINDEXED_LRECORD_IMPLEMENTATION. While the type tags were traditionally at the top of the Lisp Object, minimal tagbits move them to the bottom (the place is free because of alignment), which means that there are now exactly two tag bits, giving us four types -- character, record, and two integer types, which employ some trickery to provide 31-bit integers. Indexed lrecord implementation changes the way lrecord informatino is stored. --gung-ho will be the default beginning with 21.2.14. </gory details> In this case, --gung-ho likely sweeps the bug under the carpet.

1 participants
0 comments

Re: build problem with-mule 25 years, 6 months

Gunnar Evermann

"T. Kurosaka - Sun Professional Services" <kuro(a)Japan.Sun.COM> writes: > I received only one response to this build problem of mine. (Thank you, > Ienaga-san!) Sorry, about this. We have seen this crash a couple of times, but have not yet figured out what is causing it. If you only want a working xemacs then you can probably just supply '--gung-ho' as an extra configure option. > I need any help on this. I have the following questions. > > (1) All the statements of src/mule-coding.c are commented out by "#if 0" > I.e. src/mule-coding.c is null. Is this OK? yes. > (2) I re-ran configure with --debug but "make" still invokes cc with -xO4; > no -g is supplied. What is wrong ? use --with-cflags=-g > (3) Is there a general guideline of how to debug coredump of temacs or xemacs? > How do I stop temacs just before starting processing "update-elc.stamp", > so that temacs can be run in a single step mode from there? see FAQ 2.1.16. dbxrc defines a command 'update-elc' which you can use. To debug gc problems you should: - read the XEmacs Internals manual - try setting always_gc=1 to get a crash early - try using watchpoints, if some memory location is corrupted accidentally. I'm also still investigating this problem. good luck. Gunnar -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

2 participants
1 comments

Re: Download latest XEmacs 21.2 from CVS? 25 years, 6 months

Petr Konecny

>>>>> Jose Romildo Malaquias (Jose) said: Jose> I would like to download the latest XEmacs 21.2 from Jose> the CVs repository, but I do not know how. Following Jose> the instructions from http://cvs.xemacs.org just Jose> gives me the latest stable release, that is, Jose> XEmacs 21.0. Jose> Any help? Search the archive at: http://www.xemacs.org/list-archives/xemacs-beta/ Petr -- Time is an illusion, lunchtime doubly so. -- The Hitchhiker's Guide to the Galaxy

1 participants
0 comments

Re: Download latest XEmacs 21.2 from CVS? 25 years, 6 months

Adrian Aichner

>>>>> "Jose" == Jose Romildo Malaquias <romildo(a)urano.iceb.ufop.br> writes: Jose> I would like to download the latest XEmacs 21.2 from Jose> the CVs repository, but I do not know how. Following Jose> the instructions from http://cvs.xemacs.org just Jose> gives me the latest stable release, that is, Jose> XEmacs 21.0. Try this in the top level directory: cvs -z3 update -Pd -A -r release-21-2 HTH, Adrian Jose> Any help? Jose> José Romildo Malaquias <romildo(a)urano.iceb.ufop.br> -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Download latest XEmacs 21.2 from CVS? 25 years, 6 months

José Romildo Malaquias

I would like to download the latest XEmacs 21.2 from the CVs repository, but I do not know how. Following the instructions from http://cvs.xemacs.org just gives me the latest stable release, that is, XEmacs 21.0. Any help? José Romildo Malaquias <romildo(a)urano.iceb.ufop.br>

1 participants
0 comments

RE: Fix for (Solaris) mem corruption bug 25 years, 6 months

Damon Lipparelli

Sorry to rain on your parade, but this doesn't fix the problem for me (at least not in 21.0). I applied your patch by hand and tried re-compiling without "--gung-ho". No joy (the stack trace in the core looks similar to before). -lipp -----Original Message----- From: ge204(a)eng.cam.ac.uk [mailto:ge204＠eng.cam.ac.uk] Sent: Tuesday, May 11, 1999 7:28 AM To: xemacs-beta(a)xemacs.org; xemacs-patches(a)xemacs.org; Akiumi Hasegawa Cc: Damon Lipparelli; Christian Hudon; Glenn Barry; OGAWA Naoshi; T. Kurosaka Subject: Fix for (Solaris) mem corruption bug YES! I finally managed to fix this elusive memory corruption bug, that showed up on a couple of Solaris and HPUX builds. Akiumi Hasegawa graciously provided an account on his machine for me to debug this -- Thanks Aki! The problem was that we didn't allocate enough space for the argv[] array used for run_temacs -- somebody forgot about the trailing 0. This bug must have been there for AGES! It showed up so seldomly because DO_REALLOC doubles the existing size. In this case it will only show up when nargs=2^n-1. This also proves that all good bug-fixes are one-liners. :-) The patch is against the 21.2.13 release. This is definitely recommended for 21.1 Gunnar 1999-05-11 Gunnar Evermann <ge204(a)eng.cam.ac.uk> * emacs.c (Frun_emacs_from_temacs): (re)alloc natgs+2 entries for run_temacs_argv array -- fixes random memory corruption crash Index: src/emacs.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/emacs.c,v retrieving revision 1.82.2.10 diff -u -r1.82.2.10 emacs.c --- emacs.c 1999/03/03 16:38:47 1.82.2.10 +++ emacs.c 1999/05/11 21:40:36 ＠＠ -2014,7 +2014,7 ＠＠ total_len += wampum_all_len[ac]; } DO_REALLOC (run_temacs_args, run_temacs_args_size, total_len, char); - DO_REALLOC (run_temacs_argv, run_temacs_argv_size, nargs+1, char *); + DO_REALLOC (run_temacs_argv, run_temacs_argv_size, nargs+2, char *); memcpy (run_temacs_args, wampum, namesize); run_temacs_argv [0] = run_temacs_args;

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 1999