January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: XEmacs 21.0.60 core dumps on FreeBSD 2.2.6 25 years, 3 months

Richard Coleman

> > Here is exactly what I did. > > > 1. tar -xzf xemacs-21.0.60.tar.gz > > 2. tar -xzf xemacs-21.0.60-elc.tar.gz > > 3. ./configure > > 4. cd src > > 5. ./xemacs -vanilla > > > then the first time the mouse hits the toolbar, it cores and I get the > > following lisp backtrace. > > > Fatal error: assertion failed, file window.h, line 245, RECORD_TYPEP (_obj, lrec > ord_window) || MARKED_RECORD_P (_obj) > > That looks awfully familiar. What version of gcc are you using? If > you do `./configure --cflags="-O3 -fno-caller-saves"', does that cure > the crash? Configuring with `./configure --cflags="-O3 -fno-caller-saves"' fixed the problem. So I guess it's a compiler problem. I'm using gcc 2.7.2.1 (which is the default compiler on FreeBSD 2.2.6). But I think newer versions of FreeBSD are also using this version of gcc. So, I'm afraid this might be a common situation. At the very least, there should be some mention about this in the MACHINES file. It would be even better if configure could detect this problem and add the necessary flag. -- Richard Coleman coleman(a)math.gatech.edu

1 participants
0 comments

Re: XEmacs 21.0.60 core dumps on FreeBSD 2.2.6 25 years, 3 months

SL Baur

Richard Coleman <coleman(a)math.gatech.edu> writes in xemacs-beta(a)xemacs.org: >> Do you have anything special going on with display-time in your .emacs, >> or can I expect to reproduce this with a bare-ass package-less XEmacs >> and the single line `(display-time)' in .emacs? I tried that and it didn't crash. > Ok, I spoke too quickly. I tried again, and the core dumps happens > without reference to any package. It actually happens whenever I put > the mouse over the toolbar (but nowhere else). I see. > Here is exactly what I did. > 1. tar -xzf xemacs-21.0.60.tar.gz > 2. tar -xzf xemacs-21.0.60-elc.tar.gz > 3. ./configure Excellent. This is a sequence that should be tested. > 4. cd src > 5. ./xemacs -vanilla > then the first time the mouse hits the toolbar, it cores and I get the > following lisp backtrace. ... > Fatal error: assertion failed, file window.h, line 245, RECORD_TYPEP (_obj, lrecord_window) || MARKED_RECORD_P (_obj) That looks awfully familiar. What version of gcc are you using? If you do `./configure --cflags="-O3 -fno-caller-saves"', does that cure the crash? ... > What operating system and machine description files should XEmacs use? > `s/freebsd.h' and `m/intel386.h' > What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch

1 participants
0 comments

Re: XEmacs 21.0.60 core dumps on FreeBSD 2.2.6 25 years, 3 months

Richard Coleman

> Do you have anything special going on with display-time in your .emacs, > or can I expect to reproduce this with a bare-ass package-less XEmacs > and the single line `(display-time)' in .emacs? Ok, I spoke too quickly. I tried again, and the core dumps happens without reference to any package. It actually happens whenever I put the mouse over the toolbar (but nowhere else). Here is exactly what I did. 1. tar -xzf xemacs-21.0.60.tar.gz 2. tar -xzf xemacs-21.0.60-elc.tar.gz 3. ./configure 4. cd src 5. ./xemacs -vanilla then the first time the mouse hits the toolbar, it cores and I get the following lisp backtrace. -- Richard Coleman coleman(a)math.gatech.edu Fatal error: assertion failed, file window.h, line 245, RECORD_TYPEP (_obj, lrecord_window) || MARKED_RECORD_P (_obj) Fatal error (6). Your files have been auto-saved. Use `M-x recover-session' to recover them. Please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /home/rcoleman/xemacs/xemacs-21.0.60/src/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: redisplay-echo-area() # bind (inhibit-read-only zmacs-region-stays stdout-p frame message) raw-append-message("Paste from clipboard" #<x-frame "emacs" 0x8fd> nil) # bind (stdout-p frame message label) append-message(help-echo "Paste from clipboard" nil nil) # bind (stdout-p frame message label) display-message(help-echo "Paste from clipboard") # bind (mess) show-help-echo("Paste from clipboard") # bind (hstring pointer vars help button user-pointer user-pointer1 glyph-extent glyph-extent1 extent point modeline-string modeline-point buffer window frame event) default-mouse-motion-handler(#<motion-event 244, -3>) next-command-event() byte-code("..." [add-timeout startup-message-timeout #<compiled-function (ignore) "...(5)" [nil ... ...] 3> nil timeout startup-splash-frame sit-for 0 next-command-event unread-command-event] 4) # (catch timeout ...) # (unwind-protect ...) # bind (timeout) command-line-1() # bind (command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) uname -a: FreeBSD phaedrus.cmb.net 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Wed Mar 25 02:28:49 GMT 1998 jkh＠time.cdrom.com:/usr/src/sys/compile/GENERIC i386 ./configure XEmacs 21.0-b60 "Poitou60" configured for `i386-unknown-freebsd2.2.6'. Where should the build process find the source code? /home/rcoleman/xemacs/xemacs-21.0.60 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/freebsd.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 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/X11R6/include Where do we find X Windows libraries? /usr/X11R6/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 native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "flock" for locking mail spool files. 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: XEmacs 21 /vs./ my keyboard: I want my DEL back 25 years, 3 months

Jan Vroonhof

I just wanted to inject some comments into this discussion. 1. No Martin I am not responsible for code in this case. I was involved in some discussions about it. 2. The change is NOT documented in the NEWS file! Ouch! 3. Karl, you call to 'revert to the XEmacs 20.4 system' which just worked. Well maybe it did for you but I suggest you read some of the XEmacs and linux help groups.. I helped over a dozen people in the last month alone to help getting their backspace to work. See 4. 4. You seem think XEmacs 20.4 did no translations. Well it did. It unconditionally translates '127' to 'delete', regardless of terminal try and/or terminal settings. This means you need to do a (puthash ?\^? keyboard-translate-table 'backspace) which works only most of the time and more importantly you cannot expect newbies to come up with this. What ever you might think about the new mapping at the very least it can be switched off. 5 .Pre XEmacs 20 versions even did this translation under X (i.e. trying to follow the "Backspace is just a new name for Delete" hardline unix guru approach. This causes lots of problems. 6. Apparently XEmacs 21.x with delete-key-deletes-forward t now does what the majority of its user expect of it on unconfigured - Solaris Console - Linux Console - Xfree86 XTerms which covers the overwhelming majority of cases where 'XEmacs -nw' is used nowadays. That's real progress not pseudo progress. > You're entitled to any opinion you wish to hold, and I'm entitled to > mine, but let's just make it bloody damn clear that it is *you* who > are farting around with default behavior that has existed in Emacs for > something like 15 years, And at least for the last 7 years it has caused problems for both new and old users (probably longer, but that is when I started using Emacs). > all in the name of pseudo-"progress" embodied > by the Keymap Purity Hit Squad. Note that it is really keysym purity. In XEmacs 21.0 the-key-that-deletes-backwards is 'backspace' (used to be 'delete') the-key-that-can-delete-forwards is 'delete' (previously unavailable). This transition has been going as of XEmacs 20.3 and it is just that the tty code is now aware of the change. Yes this is incompatile but the people effected by this change are a now a small minority and moreover they are also the people that can be expect to know how to change defaults (thats why it is VERY bad that it is not in NEWS). Jan

1 participants
0 comments

Re: XEmacs 21.0.60 core dumps on FreeBSD 2.2.6 25 years, 3 months

SL Baur

Richard Coleman <coleman(a)math.gatech.edu> writes in xemacs-beta(a)xemacs.org: ... > But, getting a core dump due to a missing package (especially something > common like display-time) is pretty harsh. Yup. Do you have anything special going on with display-time in your .emacs, or can I expect to reproduce this with a bare-ass package-less XEmacs and the single line `(display-time)' in .emacs? I'll take a quick look at it when I get finished uploading 21.0.61. > Especially since what I was attempting will soon become a common > action (downloading just the base package and running it without > modifying my .emacs). We have so many build-time options that relatively few combinations regularly get tested out. Things are somewhat better now since distribution-builds are now being done with bare-ass naked feature-free XEmacs binaries, but there has been much breakage.

1 participants
0 comments

Re: 21.0 vs 21.2 25 years, 3 months

SL Baur

Tor Arntsen <tor(a)spacetec.no> writes in xemacs-beta(a)xemacs.org: ... > With two trees you can still see that they are 'one' source tree because > you can do > cd xemacs-21.2; cvs tag start_myfix INSTALL; <edit INSTALL> > cvs commit -m "Corrected configure instructions" INSTALL > cd ../xemacs-22.0; cvs -q update -jstart_myfix -jrelease-21-2 INSTALL > cvs commit -m "merged fixes from 21.2 branch to 22.0 branch" > instead of re-implementing the changes in the second branch. Cute. I've never been brave[1] enough to try out stuff like that. Will it still work after a lot of changes have been committed? ie. after divergence has set in? Hmmm. The man page says a date may be used instead of tag. That sounds cleaner if it works. > For people with only read access (e.g. like me) the fact that the two > versions exist in the same source tree at the repository is of no big > importance (except for the fact that it's good to know :-) > (jumping in with too many cvs comments maybe.. it's a habit I guess, I'm > responsible for the cvs stuff where I work) Please keep it up. It's a pity you weren't around in December of 1996 when things were first being set up. Footnotes: [1] And I'm less brave now after 4 successive 1.10 releases that don't pass regression tests ... :-(

1 participants
0 comments

Re: 21.0 vs 21.2 25 years, 3 months

Tor Arntsen

>> If you wish to track both versions use two XEmacs source trees. Check >> out one with the default branch, eg. something like > >Ugh. Two source trees? I thought one of the purposes of CVS was to >have a unified version of the source. Why is this? There is only one tree in the repository, but as it is impossible to work on different versions of the same file in the same file at the same time (unless you work in the quantum world ;-) then you'll have to check out the different versions to different places. Of course you can also flip between versions on a subdirectory level, you don't have to keep two trees or two full trees if you don't want to. But it can easily get messy if you are not careful. With two trees you can still see that they are 'one' source tree because you can do cd xemacs-21.2; cvs tag start_myfix INSTALL; <edit INSTALL> cvs commit -m "Corrected configure instructions" INSTALL cd ../xemacs-22.0; cvs -q update -jstart_myfix -jrelease-21-2 INSTALL cvs commit -m "merged fixes from 21.2 branch to 22.0 branch" instead of re-implementing the changes in the second branch. For people with only read access (e.g. like me) the fact that the two versions exist in the same source tree at the repository is of no big importance (except for the fact that it's good to know :-) - Tor (jumping in with too many cvs comments maybe.. it's a habit I guess, I'm responsible for the cvs stuff where I work)

2 participants
1 comments

Re: XEmacs 21.0.60 core dumps on FreeBSD 2.2.6 25 years, 3 months

Richard Coleman

> > After getting a core dump with 21.2.8, I thought I would > > try 21.0.60 and see if I had better luck. I also get a core > > dump with this version. > > Lisp backtrace follows: > > redisplay-echo-area() # bind (inhibit-read-only zmacs-region-stays > stdout-p frame message) raw-append-message("Error in init file: > Symbol's function definition is void: display-time" #<x-frame "emacs" > 0x8fd> nil) > > This error is normal because you haven't the package time installed and > so he couldn't use the function display-time. But, getting a core dump due to a missing package (especially something common like display-time) is pretty harsh. Especially since what I was attempting will soon become a common action (downloading just the base package and running it without modifying my .emacs). -- Richard Coleman coleman(a)math.gatech.edu

1 participants
0 comments

Re: 21.0 vs 21.2 25 years, 3 months

SL Baur

Tor Arntsen <tor(a)spacetec.no> writes in xemacs-beta(a)xemacs.org: > On Jan 4, 11:52, SL Baur wrote: > [...] >> cvs -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout xemacs -d xemacs-21.0 Should be: cvs -z3 -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout \ -d xemacs-21.0 xemacs > [...] >> cvs -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout \ >> -rrelease-21-2 xemacs -d xemacs-21.2 and: cvs -z3 -d :ext:steveb＠cvs.xemacs.org:/usr/CVSroot checkout \ -rrelease-21-2 -d xemacs-21.2 xemacs [also adding the `-z3' compression flags I forgot] >> for the experimental 21.2 sources. This sequence will use the >> subdirectory xemacs-21.0/ to store the stable version and xemacs-21.2 > The final -d xemacs-21.2 has to be put *before* the module name > (xemacs), i.e. Oops. I misread my notes. You are correct and what I originally wrote is wrong.

1 participants
0 comments

Re: 21.0 vs 21.2 25 years, 3 months

SL Baur

Richard Coleman <coleman(a)math.gatech.edu> writes in xemacs-beta(a)xemacs.org: Peter> If I want to track the 21.0 sources, must I `cvs update -R Peter> release-21-0' in said directory? ... >> >> If you wish to track both versions use two XEmacs source trees. Check >> out one with the default branch, eg. something like > Ugh. Two source trees? I thought one of the purposes of CVS was to > have a unified version of the source. Why is this? ? It's one CVS tree. You need two checked-out source trees if you wish to track both branches. I don't see any other way to do it easily. The way things are being kept in synch (for the most part), I don't see a particular need for anyone to track both branches unless they're really gung-ho about it. > Also, what about adding tags like xemacs-current and xemacs-stable > that would track these two branches without dealing with version > numbers. Good idea. > Also, my understanding is that 21.0 is the main part of the tree > and 21.2 is a branch. Correct. Assuming XEmacs doesn't die out in the interim, I think this should be reversed in the future -- ie. the bleeding edge version is always the default branch and the stable version is the forked branch. > Is there any chance of eventually flipping this, so that the > developmental sources are always the main line of the tree? Yes. The plan has been to do this when 21.0.final is made.

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