April 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Adrian Aichner

I just hit following assertion: Fatal error: assertion failed, file c:\Hacking\xemacs\xemacs-21.2\nt\..\src\lstream.h, line 33, RECORD_TYPEP (obj, lrecord_type_lstream) I was in gnus-version "Gnus v5.8.8", trying to get new mail via pop. Best regards, Adrian Call Stack: NTDLL! 77f9eea9() error_check_lstream(long 20488640) line 33 + 56 bytes nt_send_process(long 128950312, lstream * 0x0265f968) line 1086 + 12 bytes send_process(long 128950312, long 127527308, const unsigned char * 0x00000000, int 0, int 45) line 1001 + 23 bytes Fprocess_send_string(long 128950312, long 127527308, long 20488640, long 20488640) line 1133 + 26 bytes Ffuncall(int 3, long * 0x0082e128) line 3528 + 168 bytes execute_optimized_program(const unsigned char * 0x0082e314, int 6, long * 0x00e67320) line 746 + 16 bytes Fbyte_code(long 42749004, long 15102736, long 13) line 2405 + 38 bytes Feval(long 41881224) line 3331 + 187 bytes condition_case_1(long 41747188, long (long)* 0x010718dc Feval(long), long 41881224, long (long, long)* 0x0106ebb5 run_condition_case_handlers(long, long), long 20459888) line 1651 + 7 bytes condition_case_3(long 41881224, long 20459888, long 41747188) line 1732 + 27 bytes execute_rare_opcode(long * 0x0082e7b0, const unsigned char * 0x02966951, int 143) line 1271 + 19 bytes execute_optimized_program(const unsigned char * 0x02966858, int 8, long * 0x02990ec8) line 656 + 17 bytes funcall_compiled_function(long 46400120, int 2, long * 0x0082ea9c) line 518 + 53 bytes Ffuncall(int 3, long * 0x0082ea98) line 3563 + 17 bytes execute_optimized_program(const unsigned char * 0x029cddf0, int 3, long * 0x029d7850) line 746 + 16 bytes funcall_compiled_function(long 43740704, int 2, long * 0x0082ed70) line 518 + 53 bytes Ffuncall(int 3, long * 0x0082ed6c) line 3563 + 17 bytes execute_optimized_program(const unsigned char * 0x02c85f38, int 6, long * 0x029ef8e0) line 746 + 16 bytes funcall_compiled_function(long 43678356, int 2, long * 0x0082f050) line 518 + 53 bytes Ffuncall(int 3, long * 0x0082f04c) line 3563 + 17 bytes execute_optimized_program(const unsigned char * 0x029cdaa8, int 7, long * 0x029ef768) line 746 + 16 bytes funcall_compiled_function(long 43678328, int 2, long * 0x0082f2b0) line 518 + 53 bytes Feval(long 43292032) line 3388 + 20 bytes condition_case_1(long 43279464, long (long)* 0x010718dc Feval(long), long 43292032, long (long, long)* 0x0106ebb5 run_condition_case_handlers(long, long), long 20488640) line 1651 + 7 bytes condition_case_3(long 43292032, long 20488640, long 43279464) line 1732 + 27 bytes execute_rare_opcode(long * 0x0082f570, const unsigned char * 0x02c87910, int 143) line 1271 + 19 bytes execute_optimized_program(const unsigned char * 0x02c878d8, int 5, long * 0x029ef610) line 656 + 17 bytes funcall_compiled_function(long 43678300, int 0, long * 0x0082f850) line 518 + 53 bytes Ffuncall(int 1, long * 0x0082f84c) line 3563 + 17 bytes execute_optimized_program(const unsigned char * 0x02d26b08, int 3, long * 0x02c88c80) line 746 + 16 bytes funcall_compiled_function(long 46854972, int 1, long * 0x0082fb20) line 518 + 53 bytes Ffuncall(int 2, long * 0x0082fb1c) line 3563 + 17 bytes Fcall_interactively(long 33754060, long 20488640, long 20488640) line 940 + 22 bytes Fcommand_execute(long 33754060, long 20488640, long 20488640) line 2970 + 17 bytes execute_command_event(command_builder * 0x01da7af8, long 43674260) line 3911 + 25 bytes Fdispatch_event(long 43674260) line 4203 + 70 bytes Fcommand_loop_1() line 583 + 9 bytes command_loop_1(long 20488640) line 495 condition_case_1(long 20488280, long (long)* 0x01051046 command_loop_1(long), long 20488640, long (long, long)* 0x01050a60 cmd_error(long, long), long 20488640) line 1651 + 7 bytes command_loop_3() line 256 + 35 bytes command_loop_2(long 20488640) line 269 internal_catch(long 20318408, long (long)* 0x01050bb0 command_loop_2(long), long 20488640, int * volatile 0x00000000) line 1317 + 7 bytes initial_command_loop(long 20488640) line 305 + 25 bytes STACK_TRACE_EYE_CATCHER(int 1, char * * 0x00e62620, char * * 0x00e62c00, int 0) line 2346 main(int 1, char * * 0x00e62620, char * * 0x00e62c00) line 2714 mainCRTStartup() line 338 + 17 bytes KERNEL32! 77e992a6() -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

1 participants
0 comments

XEmacs v21.4.1 hung with fatal i/o error 23 years, 7 months

Tony Lam

I got this after running XEmacs for couple of days. xemacs-21.4.1: Fatal I/O Error 0 (Error 0) on display connection ":0.0" after 1861692 requests (1861691 known processed) with 4 events remaining. (gdb) where #0 0xfed18228 in _poll () from /usr/lib/libc.so.1 #1 0xfeccb808 in select () from /usr/lib/libc.so.1 #2 0xfefbb5c4 in _XtWaitForSomething () from /usr/openwin/lib/libXt.so.4 #3 0xfefc0798 in XtAppPending () from /usr/openwin/lib/libXt.so.4 #4 0x17bb24 in drain_X_queue () #5 0x17bc50 in emacs_Xt_event_pending_p () #6 0xb95a0 in event_stream_event_pending_p () #7 0xba1bc in detect_input_pending () #8 0xbb7a4 in run_pre_idle_hook () #9 0xbbb74 in Fnext_event () #10 0x6bf7c in Fcommand_loop_1 () #11 0x895dc in condition_case_1 () #12 0x6b894 in command_loop_3 () #13 0x6b8c8 in command_loop_2 () #14 0x8923c in internal_catch () #15 0x6bac0 in initial_command_loop () #16 0x855f0 in xemacs_21_4_1_sparc_sun_solaris2_7 () #17 0x85e7c in main () Tony

1 participants
0 comments

MinGW Problem 23 years, 7 months

Craig Lanning

I have been poking around trying to get the MinGW (-mno-cygwin) port working again and found the following error while running the command './xemacs -nd -batch -l /xemacs/xe-21-4/src/../lisp/update-elc.el': Error before initialization is complete! Fatal error: assertion failed, file eval.c, line 1879, abort() Does anyone have any idea about what is happening, where I should look, or what I should do to get more info? Craig P.S. Below is the Installation file built by configure: uname -a: CYGWIN_98-4.10 CRAIGL 1.3.1(0.38/3/2) 2001-04-24 20:01 i586 unknown ./configure '--site-prefixes=/mingw' '--pdump' 'i586-pc-mingw32' XEmacs 21.4.1 "Copyleft" configured for `i586-pc-mingw32'. Compilation / Installation: Source code location: /xemacs/xe-21-4 Installation prefix: /usr/local Additional prefixes: /mingw Operating system description file: `s/mingw32.h' Machine description file: `m/intel386.h' Compiler: gcc -g -Wall -Wno-switch -Winline -Wmissing-prototypes -Wshadow -Wsign-compare -Wpointer-arith Relocating allocator for buffers: default GNU version of malloc: yes Window System: Compiling in support for the Microsoft window system. Using MS-Windows menubars. Using MS-Windows scrollbars. Using MS-Windows dialog boxes. Using MS-Windows native widgets. TTY: Images: Compiling in support for GIF images (builtin). Compiling in support for XPM images. Compiling in support for PNG images. Compiling in support for JPEG images. Compiling in support for TIFF images. Compiling in support for X-Face message headers. Sound: Compiling in support for sound (native). Databases: Internationalization: Compiling in support for file coding. Mail: Compiling in support for POP mail retrieval. Other Features: Compiling in support for dynamic shared object modules. Using the new portable dumper.

2 participants
1 comments

Compilation of packages from CVS; problems and workarounds 23 years, 7 months

Hannu Koivisto

Greetings, Now that I finally got XEmacs 21.4.1 compiled and installed, I thought to try to compile all packages from CVS (updated few minutes ago). First of all, INSTALL tells to do `make autoloads' and `make install', but I don't want to compile and install in a single step, so I'm running `make all' and `make just-install' instead of `make install'. * compilation of patcher.el in package xemacs-devel fails because sendmail cannot be found. I think this is because xemacs-devel doesn't require mail-lib in its Makefile. At least adding mail-lib to REQUIRES fixed the problem. * generation of vm.info in package vm fails because texinfmt couldn't be loaded. I added: -eval '(push "../../wp/texinfo/" load-path)' -l informat to the command line that generates vm.info to "fix" the problem (this obviously doesn't consider XEMACS_NATIVE_NT_NEEDS_EXTRA_QUOTING etc.) * compilation of w3 failed because advice couldn't be loaded. I added ../../libs/xemacs-base to the load-path in a similar way as above. * generation of ja.info in package tm failed --- reason and fix similar to the second problem. However, even after that fix I get: ... make[3]: Entering directory `/.../xemacs-packages-compiled/comm/tm/texi' /usr/local/xemacs-21.4/bin/xemacs -batch -q -no-site-file tm-ja.texi \ -eval '(unless (featurep (quote mule)) (kill-emacs 0))' \ -eval '(push "../../../wp/texinfo/" load-path)' -l informat \ -l texinfmt -f texinfo-format-buffer \ -eval '(setq file-coding-system (quote iso-2022-7))' \ -eval '(save-buffer 0)' File mode specification error: (wrong-type-argument stringp nil) Formatting Info file... ... * generation of mew info files in package mew failed --- reason and fix similar to the second problem. * compilation of ILISP failed because ilisp-mak.el tried to load comint and it couldn't be found. I added ../../libs/xemacs-base to the PRELOADS and added $(PRELOADS) to the command line that loads ilisp-mak.el. Compilation of hyperspec failed because browse-url and thingatpt couldn't be found. I added ../../libs/{mail-lib,fsf-compat} to PRELOADS and added $(PRELOADS) to the command line that compiles hyperspec.el. * generation of calc.info in package calc failed --- reason and fix similar to the second problem. * ditto for generation of info files in package mule/lookup * ditto for generation of info files in package mule/skk After these fixes `make all' finally succeeded, just like `make just-install' after that. Sorry, I didn't prepare patches because I don't know if this kind of bootstrapping is even supposed to work, I'd rather not import 70MB of packages to a local repository, I don't know if relative paths and explicitly modifying command lines everywhere are good ideas and because I thought I would get away with just a few problems, I didn't do my fixes with proper care and just quickly hacked things to work for myself. -- Hannu Please don't send copies of list mail

1 participants
0 comments

Unable to install 21.4.1 to Debian GNU/Linux x86 potato 23 years, 7 months

Hannu Koivisto

Greetings, I checked out the head of the release-21-4 branch (21.4.1) from CVS, configured it with: ./configure --prefix=/usr/local/xemacs-21.4 --with-gif=yes --with-sound=native --with-mule --without-canna --without-wnn --without-wnn6 --datadir=/usr/local/xemacs-21.4/share --statedir=/var/lib --infodir=/usr/local/xemacs-21.4/info --mandir=/usr/local/xemacs-21.4/man --with-xpm --with-xface --with-jpeg --with-png --with-gcc --with-gnu-make --with_menubars=lucid --with_scrollbars=lucid --with_dialogs=athena --site-includes="/usr/include/db2" I tried to configure just native sound support (I recall seeing someone here mentioning about problems with ESD) and no ESD but obviously misunderstood the usage of --with-sound option because configure said it would compile native sound _and_ ESD support. Should I really have disabled all other types except native in addition? Feels a bit weird interface design to me. When I try to install with `make install', I get following kind of error messages: Loading .../xemacs-21.4-compiled/src/../lisp/make-docfile.el... Loading very-early-lisp... Loading find-paths.el... Loading packages.el... Loading setup-paths.el... Loading dump-paths.el... Loading .../xemacs-21.4-compiled/lisp/dumped-lisp.el... "Error: Library file backquote not found" rm -f ../lib-src/DOC; \ ...and: Loading .../xemacs-21.4-compiled/src/../lisp/make-docfile.el... Loading very-early-lisp... Loading find-paths.el... Loading packages.el... Loading setup-paths.el... Loading dump-paths.el... File error: "Cannot open load file", "custom" ...and: ./temacs -nd -batch -l \ .../xemacs-21.4-compiled/src/../lisp/loadup.el dump Loading /xemacs-21.4-compiled/src/../lisp/loadup.el... Using load-path (.../xemacs-21.4-compiled/lisp) Using module-load-path (.../xemacs-21.4-compiled/modules) Loading very-early-lisp... Loading .../xemacs-21.4-compiled/lisp/dumped-lisp.el... Loading .../xemacs-21.4-compiled/lisp/backquote.elc... Loading .../xemacs-21.4-compiled/lisp/bytecomp-runtime.elc... Loading .../xemacs-21.4-compiled/lisp/find-paths.elc... Loading .../xemacs-21.4-compiled/lisp/packages.elc... Loading .../xemacs-21.4-compiled/lisp/setup-paths.elc... Loading .../xemacs-21.4-compiled/lisp/dump-paths.elc... Load file subr: not found Fatal error during load, aborting make[1]: *** [xemacs] Error 1 make[1]: Leaving directory `/.../xemacs-21.4-compiled/src' make: *** [src] Error 2 Concerning those few files that `make install' managed to install, I found directory /usr/local/xemacs-21.4/share/xemacs-21.4.1/i686-pc-linux and executables under it. This doesn't make sense, INSTALL says: The `--prefix=PREFIXDIR' option specifies where the installation process should put XEmacs and its data files. This defaults to `/usr/local'. - XEmacs (and the other utilities users run) go in PREFIXDIR/bin (unless the `--exec-prefix' option says otherwise). - The architecture-independent files go in PREFIXDIR/lib/xemacs-VERSION (where VERSION is the version number of XEmacs, like `21.0'). and also: `libdir' indicates where to put architecture-specific data files that XEmacs refers to as it runs; it too defaults to `/usr/local/lib'. We create the following subdirectories under `libdir': - `xemacs-VERSION/CONFIGURATION-NAME', containing executable programs used by XEmacs that users are not expected to run themselves and the DOC file. I specified --prefix and I didn't specify --exec-prefix and I didn't specify libdir so I expect those binaries to go to /usr/local/xemacs-21.4/lib/xemacs-21.4.1/i686-pc-linux. Did I do something wrong or is 21.4* still this broken? -- Hannu Please don't send copies of list mail

2 participants
8 comments

bogus setting of zmacs_region_stays 23 years, 7 months

Ben Wing

someone pointed out how rectangle mousing isn't sticky. i spent a long time debugging this and finally tracked it down to a call to narrow-to-region, which has at its end: /* Changing the buffer bounds invalidates any recorded current column. */ invalidate_current_column (); narrow_line_number_cache (buf); zmacs_region_stays = 0; <----------------------------- return Qnil; } various other functions [erase-buffer, insert commands] have this. it's completely bogus. i've removed all of them and so far no problems. i'm planning on committing this at some point to 21.5. -- ben I'm sometimes slow in getting around to reading my mail, so if you want to reach me faster, call 520-661-6661. See http://www.666.com/ben/chronic-pain/ for the hell I've been through.

2 participants
1 comments

Re: [Jonas S Karlsson <jonas_s_karlsson@yahoo.com>] windows installer fails on "tm-1.26..." 23 years, 7 months

Adrian Aichner

>----- Ursprüngliche Nachricht ----- >Absender: youngs(a)xemacs.org >Betreff: Re: [Jonas S Karlsson <jonas_s_karlsson(a)yahoo.com>] windows installer fails on "tm-1.26..." >Empfänger: XEmacs Beta >Datum: 27. Apr 2001 10:25 > > |--==> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: > > >>>>>>"SY" == Steve Youngs <youngs(a)xemacs.org> writes: > SY> |--==> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: > APA> Hello Steve, > > APA> do you know this problem? > > APA> The windows automatic installer fails on the "tm-..." > APA> file since this one has a filesize of 332323 > APA> but it "expects" 332673 bytes... > > SY> Yep. I fixed it a couple of days ago. > > APA> Fraid Knot! > > Hopefully, it's right now. Yes, this works for me now. Thanks, Steve! Adrian > > -- > |---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---| > | XEmacs - It's not just an editor. | > | It's a way of life. | > |------------------------------------<youngs(a)xemacs.org>---| > >

1 participants
0 comments

[Jonas S Karlsson <jonas_s_karlsson@yahoo.com>] windows installer fails on "tm-1.26..." 23 years, 7 months

Adrian Aichner

Hello Steve, do you know this problem? Best regards, Adrian -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

2 participants
4 comments

RE: [c.e.x] Re: Change in kill-region in 21.4? 23 years, 7 months

Jerker Haglund

> Gunnar Evermann wrote: > > > > This seems to explain some of the marking oddities we have seen > > recently. Any comments by whoever implemented the shifted-key stuff? > > my bug. a fix will be present shortly. Perhaps you could double check the rectangle marking as well please, M-mouse left+drag, the rectangle doesn't seem to stick anymore, worked in 21.1.13. This was on NT. /J. Haglund

2 participants
1 comments

Re: Guile support in XEmacs. 23 years, 7 months

monkeyiq

just in case the relavant people are unaware of swig, I would like to post that as an option. www.swig.org I use it in witme and it allows one to wrap C/C++ code and interface to guile/perl/python/Java and other HLLs. Maybe there would be a common lisp module made for it, so that people who want to script emacs in python can, and people who want LISP can. Just thought it highlight this as an option for the future. -- --------------------------------------------------- It's the question, http://witme.sourceforge.net If you think education is expensive, try ignorance. -- Derek Bok, president of Harvard

2 participants
1 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 April 2001