December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Failure compiling xemacs-21.2-b3 on windows 98. 25 years, 10 months

Dan Glastonbury

G'Day, (I'm sure whether this should go to xemacs-nt or to here?!) I've been trying to build xemacs-21.2-b3 on windows 98 with MSVC++ 5.0, but to no avail. I've followed the instructions in nt/README; I built the jpeg, png, and xpm libraries and I tried to build xemacs with: nmake -f xemacs.mak HAVE_XPM=1 XPM_DIR="d:\xpm-3.4k" HAVE_JPEG=1 JPEG_DIR="d:\jpeg-6b" HAVE_PNG=1 PNG_DIR="d:\libpng" ZLIB_DIR="d:\zlib" WITH_GUNGHO=1 PACKAGEPATH="d:\xemacs-21.0\packages" INSTALL_DIR="d:\xemacs-21.0" All compiles fine, but when trying to link temacs the following symbols are unresolved: from dired.c: getpwent, setpwent, endpwent from filelock.c: symlink, rindex, index, readlink The password entry ones make sense, as do the link ones, as windows 98 doesn't have links or password files. Are there supposed to be stubs for these functions under windows 95/98? I looked through the source tree and read the building xemacs under windows document from Hrvoje's home page but I didn't see any mention of caveats of build under windows 95/98. As for the the rindex/index problem Martin recently sent a patch that should fix that problem. cheers Dan -- Dan Glastonbury <dan at adelaide.maptek.com.au> `Network is unreachabl'

1 participants
0 comments

Re: Asking me not to work on XEmacs 25 years, 10 months

Hrvoje Niksic

Richard Stallman <rms(a)gnu.org> writes: > Looking at the words in my old message, it appears I asked you to > work on projects that contribute to Emacs and XEmacs at the same > time. And, in addition, not to work on those that contribute only to XEmacs. > You seem to be angry at me; perhaps this is a case of seeing what > you expect to see. That's a possibility, but I don't consider it likely. After a year and a half, I'm parsing that message just like I did at the time I received it. > I didn't say before, and I won't say now, that I have never asked > anyone to stop working on XEmacs. But you did say that you have never asked me not to work on XEmacs, which is false, as witnessed by the message above. Of course, I don't consider your doing so a "terrible crime", but I do consider it stooping *very* low -- and I know I don't want to follow you there, ever. Your further explanation why I should not work on XEmacs was also "interesting", but I think I'll spare the readership more old messages. I mailed that one because you forced me so by claiming that you've never asked me to work on XEmacs, thus insulting my recollection and intelligence. > In any case, in a situation of rivalry where one side reacts to the > other, it is unfair to discuss only my faults and not those of the > other side. I won't say more about this now, because I'd prefer to > spend the time on something other than counteraccusations. I'd > rather we drop the one subject than raise the other. I agree in the principle; however, my conscience is clear. If you have something to say, say it. You've never had compunctions about doing that.

1 participants
0 comments

background and foreground colors 25 years, 10 months

Larry Ayers

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.0 "Poitou60" [Lucid] (i586-pc-linux) of Fri Dec 11 1998 on liatris configured using `configure --prefix=/usr/local/xemacs-beta --with-site-lisp --package-path=/usr/local/xemacs-beta/lib/xemacs/packages --gung-ho --with-xpm --with-tiff=no --with-dialogs=athena --error-checking=none --debug=no --with-pop' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: Something new and undesirable in 21.0-beta60: when the font is changed from the Options menu the background is changed to white and the foreground is changed to black, over-riding the settings which have worked until now in my ~/.Xresources file. This didn't happen with the most recent beta in the 21.2 series. Recent keystrokes: y ) SPC l a s t SPC b u c k e t SPC o f SPC c o m p o u n d ; SPC i t SPC w i l l SPC b e SPC t h e SPC s i x t h . f7 misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user button3 misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user button2 misc-user button1 button1up button1 button1up misc-user button3 misc-user misc-user misc-user Recent messages (most recent first): Loading emacsbug...done Loading emacsbug... Font -*-Iowanoldst Bt-medium-r-*-*-*-150-*-*-*-*-iso8859-* Changing font of `gnus-x-face'... Changing font of `highlight'... Changing font of `calendar-today-face'... Changing font of `gnus-group-news-low-face'... Changing font of `gnus-group-mail-3-empty-face'... Changing font of `toolbar'... Changing font of `left-margin'...

2 participants
1 comments

about the copyrights in the splash buffer 25 years, 10 months

Didier Verna

Quoting rms: | Since 24 line terminals are still common, please keep the copyright | notice near the top where it is visible. Even with much effort, I can't manage to interpret this as "it is illegal to put the copyrights at the bottom" ... -- / / _ _ 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

2 participants
1 comments

[Success] "Poitou60" 25 years, 11 months

Rebecca Ore

With one weirdness. I'd reset my .Xdefaults to gray90 and this isn't happening now. Also, I had built the latest Mailcrypt which used gpg. I take it this was blown away -- will what we've got now use gpg or will I have to download and rebuild. Third question -- where do I get fonts again? I have tried to get koi8 fonts and downloaded some, but XEmacs isn't recognizing them. I thought the site was www.emacs.org or something like that, but couldn't get to it. Here's the installation file: uname -a: Linux ogoense.net 2.0.35 #1 Thu Jul 23 14:01:04 EDT 1998 i586 unknown ./configure '--with-mule' '--with-site-lisp' XEmacs 21.0-b60 "Poitou60" configured for `i586-pc-linux'. Where should the build process find the source code? /home/rebecca/xemacs-21.0.60 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/X11R6/include Where do we find X Windows libraries? /usr/X11R6/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 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 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: ---------------------------------------------------------

1 participants
0 comments

Re: compiles suffix (*.elc) 25 years, 11 months

Hrvoje Niksic

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > I think it is a good idea for XEmacs and Emacs installations to not > intefere with each other. Since we're the spinoff, it seems > reasonable and fair for us to be the ones to do the changing. Both us and FSF changed the format; FSF Emacs 20 .elc files are not very readable to FSF 19.34. We at least have the -compatibility flag.

1 participants
0 comments

Re: compiles suffix (*.elc) 25 years, 11 months

SL Baur

Kyle Jones <kyle_jones(a)wonderworks.com> writes in xemacs-beta(a)xemacs.org: > I think we (xemacs) should move to a different file suffix. > And we should do it now, early in the 21.2 dev cycle. How are we going to deal with XEmacs 21.0 compatibility? If changing the suffix means screwing over XEmacs 21 users, I firmly veto this change.

2 participants
1 comments

[FAILURE] 21.2.5 core dump in `insdel.c' 25 years, 11 months

Simon Josefsson

In XEmacs 21.2 "Aphrodite" [Lucid] (mips-sgi-irix6.3, Mule) of Fri Dec 11 1998 on xiphias.pdc.kth.se configured using `configure --with-mule --package-path=/usr/local/vol/xemacs-21.2.5/lib/xemacs --site-includes=/afs/pdc.kth.se/src/packages/gnu/libpng-1.0.2/sgi_63 --site-libraries=/afs/pdc.kth.se/src/packages/gnu/libpng-1.0.2/sgi_63 --prefix=/usr/local/vol/xemacs-21.2.5' I was reading a article in Gnus. Fatal error: assertion failed, file /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/insdel.c, line 364, VALID_CHARPTR_P (ptr) 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 /usr/local/vol/xemacs-21.2.5/bin/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: mm-decode-coding-region(1533 4058 koi8-r) # bind (mule-charset) # (unwind-protect ...) # bind (type encoding charset) mm-decode-body("koi8-r" 8bit "text/plain") # bind (buffer-read-only mm-charset-iso-8859-1-forced rfc2047-default-charset charset ctl cte ct case-fold-search inhibit-point-motion-hooks) # (unwind-protect ...) # (unwind-protect ...) # bind (prompt) article-decode-charset() run-hooks(article-decode-charset) # bind (do-update-line sparse-header group article) gnus-request-article-this-buffer(1378 "nnimap+pdc:INBOX.gnus") # bind (buffer-read-only) # (unwind-protect ...) # bind (result group gnus-tmp-internal-hook summary-buffer gnus-article) # (unwind-protect ...) # bind (header all-headers article) gnus-article-prepare(1378 nil) # bind (all-header article) gnus-summary-display-article(1378) # bind (article article-window endp circular lines) gnus-summary-next-page(nil) # bind (command-debug-status) call-interactively(gnus-summary-next-page) # (condition-case ... . error) # (catch top-level ...) (gdb) bt #0 0xfa92fb4 in _kill () at kill.s:15 #1 0x4b9ed8 in fatal_error_signal () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/emacs.c:264 #2 <signal handler called> #3 0xfa92fb4 in _kill () at kill.s:15 #4 0xfaf353c in _raise () at raise.c:25 #5 0xfa984f4 in abort () at abort.c:38 #6 0x4b4c28 in assert_failed () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/emacs.c:233 #7 0x5c9fc8 in bytecount_to_charcount () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/insdel.c:364 #8 0x5cb934 in buffer_insert_string_1 () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/insdel.c:374 #9 0x5d2d10 in buffer_insert_raw_string_1 () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/insdel.c:374 #10 0x5f3d54 in lisp_buffer_writer () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/lstream.c:137 #11 0x5f5e60 in Lstream_flush_out () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/lstream.c:137 #12 0x5f6270 in Lstream_flush () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/lstream.c:137 #13 0x51ba88 in decoding_flusher () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/file-coding.c:231 #14 0x5f5eec in Lstream_flush_out () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/lstream.c:137 #15 0x5f6270 in Lstream_flush () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/lstream.c:137 #16 0x51694c in encoding_flusher () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/file-coding.c:231 #17 0x5f5eec in Lstream_flush_out () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/lstream.c:137 #18 0x5f6170 in Lstream_write_1 () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/lstream.c:137 #19 0x5f65f8 in Lstream_write () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/lstream.c:137 #20 0x512090 in Fdecode_coding_region () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/file-coding.c:231 #21 0x4c0b8c in Ffuncall () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #22 0x469700 in execute_optimized_program () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:440 #23 0x46feac in funcall_compiled_function () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:527 #24 0x4c0d78 in Ffuncall () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #25 0x469700 in execute_optimized_program () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:440 #26 0x46feac in funcall_compiled_function () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:527 #27 0x4c0d78 in Ffuncall () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #28 0x4c1bf8 in run_hook_with_args_in_buffer () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #29 0x4c1d04 in run_hook_with_args () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #30 0x4c1d64 in Frun_hooks () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #31 0x4c0d0c in Ffuncall () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #32 0x469700 in execute_optimized_program () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:440 #33 0x46feac in funcall_compiled_function () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:527 #34 0x4c0d78 in Ffuncall () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #35 0x469700 in execute_optimized_program () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:440 #36 0x46feac in funcall_compiled_function () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:527 #37 0x4c0d78 in Ffuncall () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #38 0x469700 in execute_optimized_program () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:440 #39 0x46feac in funcall_compiled_function () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:527 #40 0x4c0d78 in Ffuncall () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #41 0x469700 in execute_optimized_program () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:440 #42 0x46feac in funcall_compiled_function () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/bytecode.c:527 #43 0x4c0d78 in Ffuncall () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #44 0x473574 in Fcall_interactively () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/callint.c:143 #45 0x4c56c8 in Fcommand_execute () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #46 0x541e80 in execute_command_event () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/event-stream.c:279 #47 0x542fb4 in Fdispatch_event () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/event-stream.c:279 #48 0x483024 in Fcommand_loop_1 () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/cmdloop.c:77 #49 0x48315c in command_loop_1 () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/cmdloop.c:77 #50 0x4c2e8c in condition_case_1 () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #51 0x4837f0 in command_loop_3 () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/cmdloop.c:77 #52 0x483868 in command_loop_2 () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/cmdloop.c:77 #53 0x4bbebc in internal_catch () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/eval.c:282 #54 0x483e30 in initial_command_loop () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/cmdloop.c:77 #55 0x4b9364 in xemacs_21_2_b5_mips_sgi_irix6_3 () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/emacs.c:233 #56 0x4b9448 in main () at /afs/pdc.kth.se/src/packages/gnu/emacsen/xemacs-21.2.5/xemacs-21.2.5/src/emacs.c:233 #57 0x444598 in __start () at crt1text.s:165 Current language: auto; currently asm

1 participants
0 comments

Re: [Failure, Patch filelock.c] XEmacs 21.0-b60 "Poitou60", i386-pc-win32 25 years, 11 months

Adrian Aichner

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Adrian Aichner <aichner(a)ecf.teradyne.com> writes: Jan> If CLASH_DETECTION is undefined that this file should not be compiled Jan> [this is what this message is all about]. Jan> So I think this should be fixed elsewhere. Jan> Jan Jan, you are right. I was lost in the forest in front of a large tree. My patch of src/filelock.c was evil and should not be applied. Thanks Jan, Adrian How about patching xemacs.mak instead? 1998-12-11 Adrian Aichner <aichner(a)ecf.teradyne.com> * xemacs.mak (DOC_SRC2): CLASH_DETECTION is not supported under native Windows NT. Therefore src\filelock.c is not to be compiled. (TEMACS_OBJS): Consequently, don't link in $(OUTDIR)\filelock.obj. cd d:\export\home\tmp\21.0\xemacs\ cvs diff -u nt/xemacs.mak Compilation started at Fri Dec 11 16:25:02 1998 Index: nt/xemacs.mak =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/nt/xemacs.mak,v retrieving revision 1.48 diff -u -r1.48 xemacs.mak --- xemacs.mak 1998/12/11 11:08:05 1.48 +++ xemacs.mak 1998/12/11 23:06:22 ＠＠ -622,7 +622,6 ＠＠ $(XEMACS)\src\faces.c \ $(XEMACS)\src\file-coding.c \ $(XEMACS)\src\fileio.c \ - $(XEMACS)\src\filelock.c \ $(XEMACS)\src\filemode.c \ $(XEMACS)\src\floatfns.c \ $(XEMACS)\src\fns.c ＠＠ -867,7 +866,6 ＠＠ $(OUTDIR)\faces.obj \ $(OUTDIR)\file-coding.obj \ $(OUTDIR)\fileio.obj \ - $(OUTDIR)\filelock.obj \ $(OUTDIR)\filemode.obj \ $(OUTDIR)\floatfns.obj \ $(OUTDIR)\fns.obj \ Compilation exited abnormally with code 1 at Fri Dec 11 16:25:08

3 participants
2 comments

Re: Crashes in 21.2-b5 on NT, native 25 years, 11 months

Adrian Aichner

>>>>> "Adrian" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: >>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: >>>>> "APA" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: Martin> Please test out this patch. Especially Adrian, I would Martin> appreciate if you could give me a `thumbs up' by Sunday. Martin> Untested on NT, as usual. Adrian> How about this Backtrace then? :-) Adrian> This occured after rebuilding with you patches successfully applied. Adrian> I assume it's correct that only Adrian> event-msw.c had to be re-compiled (for WidowsNT native build) Adrian> before link.exe ＠C:\WINNT\Profiles\AichnerA\tmp\nma00176. That's what Adrian> xemacs.mak did anyway. Adrian> Here's the VC++ 5.0 CallStack, edited for bandwidth: Adrian> allocate_lisp_storage(unsigned int 2044) line 482 + 3 bytes Adrian> Fcons(Lisp_Object {...}, Lisp_Object {...}) line 1143 + 71 bytes Adrian> list2(Lisp_Object {...}, Lisp_Object {...}) line 1197 + 15 bytes Adrian> throw_or_bomb_out(Lisp_Object {...}, Lisp_Object {...}, int 0, Lisp_Object Adrian> {...}, Lisp_Object {...}) line 1432 + 13 bytes Adrian> Fthrow(Lisp_Object {...}, Lisp_Object {...}) line 1468 + 28 bytes Adrian> Fsignal(Lisp_Object {...}, Lisp_Object {...}) line 2036 + 18 bytes Adrian> throw_or_bomb_out(Lisp_Object {...}, Lisp_Object {...}, int 0, Lisp_Object Adrian> {...}, Lisp_Object {...}) line 1432 + 29 bytes Adrian> ABOVE THREE LINES REPEATED 326 TIMES Adrian> Fthrow(Lisp_Object {...}, Lisp_Object {...}) line 1468 + 28 bytes Another one of these just happened after I had used CVS menus and played one game of tetris. This time the story ends right in Fcons. The comments in throw_or_bomb_out() in src/eval.c are scarey enough to give some clue to the knowledgable. All I can make of it is this: There is a warning about infinite recursion, which is what seems to be happening here: 'top-level. If this tag doesn't exist (happens during the initialization stages) we would get in an infinite recursive Fsignal/Fthrow loop, so instead we bomb out to the really-early-error-handler. There problem is: We don't bomb out in throw_or_bomb_out(): if (!bomb_out_p) tag = Fsignal (Qno_catch, list2 (tag, val)); else call1 (Qreally_early_error_handler, Fcons (sig, data)); Fcons(Lisp_Object {...}, Lisp_Object {...}) line 1143 + 125 bytes list2(Lisp_Object {...}, Lisp_Object {...}) line 1197 + 15 bytes throw_or_bomb_out(Lisp_Object {...}, Lisp_Object {...}, int 0, Lisp_Object {...}, Lisp_Object {...}) line 1432 + 13 bytes Fthrow(Lisp_Object {...}, Lisp_Object {...}) line 1468 + 28 bytes Fsignal(Lisp_Object {...}, Lisp_Object {...}) line 2036 + 18 bytes throw_or_bomb_out(Lisp_Object {...}, Lisp_Object {...}, int 0, Lisp_Object {...}, Lisp_Object {...}) line 1432 + 29 bytes Fthrow(Lisp_Object {...}, Lisp_Object {...}) line 1468 + 28 bytes Fsignal(Lisp_Object {...}, Lisp_Object {...}) line 2036 + 18 bytes throw_or_bomb_out(Lisp_Object {...}, Lisp_Object {...}, int 0, Lisp_Object {...}, Lisp_Object {...}) line 1432 + 29 bytes <MANY LINES DELETED BY ADRIAN> Fthrow(Lisp_Object {...}, Lisp_Object {...}) line 1468 + 28 bytes Fsignal(Lisp_Object {...}, Lisp_Object {...}) line 2036 + 18 bytes throw_or_bomb_out(Lisp_Object {...}, Lisp_Object {...}, int 0, Lisp_Object {...}, Lisp_Object {...}) line 1432 + 29 bytes HTH, Adrian Adrian> It occured after XEmacs had started, reading my extensive Adrian> site-start.el and .emacs (crashes usually don't happen with Adrian> -no-init-file -no-site-file, sorry). Hitting the News toolbar button, Adrian> which starts Gnus for me, crashed XEmacs-21.0-b5++++++ Adrian> Thanks for looking into this! I am confident that this is the right Adrian> way to a robust XEmacs, EVEN on WindowsNT ;-> Adrian> I'll try my best to give crash feedback. Let me know what additional Adrian> information might help. Adrian> Regards, Adrian> Adrian Martin> 1998-12-11 Martin Buchholz <martin(a)xemacs.org> Martin> * events.h (struct timeout_data): Martin> * event-tty.c (tty_timeout_to_emacs_event): Martin> * event-msw.c (mswindows_wm_timer_callback): Martin> * event-Xt.c (Xt_timeout_to_emacs_event): Martin> * event-msw.c (mswindows_cancel_dispatch_event): Martin> Make sure Lisp_Objects inside events are initialized to Adrian> Qnil, not Martin> Qnull_pointer, which is now illegal.

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