November 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Holding CTRL+G => Fatal error 22 years, 5 months

Daniel Åkerud

Holding CTRL+G pressed for a while, 10 seconds maybe, issues a fatal error. Version: Version: 21.4.1-2 (On my debian SID disttribution) Text straight from the console: ISO8:T-----XEmacs: UserObject.h (C)----L22--All------------------------------------------ [1]+ Stopped xemacs UserObject.h pok＠king:~/pok2/src/server/pokt/pokts$ fg xemacs UserObject.h Auto-save? (y or n) y Fatal error: assertion failed, file eval.c, line 3963, !gc_in_progress Fatal error (6).

2 participants
1 comments

(no subject) 22 years, 5 months

Jens Doerre

I had an XEmacs crash. It dumped the content of the first attached file to the console. In the second file you find the information about the installation. Greetings, Jens

1 participants
0 comments

21.5-b3: setting up default faces for gtk-xemacs 22 years, 5 months

John Paul Wallington

Rather than submit this to xemacs-patches immediately, I thought it would be prudent to post it here first. The problem is that an XEmacs 21.5-b3 built --with-gtk doesn't set up default faces (on my system). To reproduce, start xemacs -q -vanilla and highlight a region with the mouse; is it visible? There is code in gtk-faces.el (namely gtk-init-device-faces) to set the 'highlight' face to look like GTK_STATE_PRELIGHT and 'zmacs-region' like GTK_STATE_SELECTED but it precludes further customization via M-x customize-face or a custom-set-faces form, which is probably why it was effectively disabled by quoting its main let* form. faces.el makes some useful default faces, but the gtk defaults were commented out. So I uncommented the commented-out gtk defaults and added additional ones. -- John Paul Wallington

1 participants
1 comments

xemacs 21.4.5 crash at startup 22 years, 5 months

Daniel Kranich

Dear all, this is my first bug report, so I hope I'm doing it right. I'm running a Suse 7.3 (but a 2.4.14 kernel) on a 700 MHz Athlon with 256 MB memory; gcc version 2.95.3. After compiling xemacs 21.4.5 it crashes at startup. Configure, crash and gdb output are attached. regards daniel kranich configure --with-msw=no gives: ... XEmacs 21.4.5 "Civil Service" configured for `i686-pc-linux'. Compilation / Installation: Source code location: /home/daniel/xemacs-21.4.5 Installation prefix: /usr/local Operating system description file: `s/linux.h' Machine description file: `m/intel386.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wshadow Relocating allocator for buffers: no GNU version of malloc: yes - Using Doug Lea's new malloc from the GNU C Library. Window System: Compiling in support for the X window system: - X Windows headers location: /usr/X11/include - X Windows libraries location: /usr/X11/lib - Handling WM_COMMAND properly. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Using Motif native widgets. TTY: Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). 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. Sound: Compiling in support for sound (native). Databases: Compiling in support for Berkeley database. Compiling in support for GNU DBM. Internationalization: Mail: Compiling in support for "dot-locking" mail spool file locking method. Other Features: Compiling in support for dynamic shared object modules. /home/daniel/xemacs-21.4.5/src/xemacs gives: Fatal error (11). ... Lisp backtrace follows: # bind (frame-being-created) make-frame(nil #<x-device on ":0.0" 0x1bbc>) frame-initialize() # bind (debugger debug-on-error command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) gdb gives: GNU gdb 20010316 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-suse-linux"... Core was generated by `src/xemacs'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/X11R6/lib/libXm.so.2...done. Loaded symbols for /usr/X11R6/lib/libXm.so.2 Reading symbols from /usr/lib/libtiff.so.3...done. Loaded symbols for /usr/lib/libtiff.so.3 Reading symbols from /usr/lib/libpng.so.2...done. Loaded symbols for /usr/lib/libpng.so.2 Reading symbols from /usr/lib/libjpeg.so.62...done. Loaded symbols for /usr/lib/libjpeg.so.62 Reading symbols from /lib/libz.so.1...done. Loaded symbols for /lib/libz.so.1 Reading symbols from /usr/X11R6/lib/libXpm.so.4...done. Loaded symbols for /usr/X11R6/lib/libXpm.so.4 Reading symbols from /usr/X11R6/lib/libXmu.so.6...done. Loaded symbols for /usr/X11R6/lib/libXmu.so.6 Reading symbols from /usr/X11R6/lib/libXt.so.6...done. Loaded symbols for /usr/X11R6/lib/libXt.so.6 Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Loaded symbols for /usr/X11R6/lib/libXext.so.6 Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Loaded symbols for /usr/X11R6/lib/libX11.so.6 Reading symbols from /usr/X11R6/lib/libSM.so.6...done. Loaded symbols for /usr/X11R6/lib/libSM.so.6 Reading symbols from /usr/X11R6/lib/libICE.so.6...done. Loaded symbols for /usr/X11R6/lib/libICE.so.6 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /usr/lib/libdb-3.1.so...done. Loaded symbols for /usr/lib/libdb-3.1.so Reading symbols from /usr/lib/libgdbm.so.2...done. Loaded symbols for /usr/lib/libgdbm.so.2 Reading symbols from /usr/lib/libgpm.so.1...done. Loaded symbols for /usr/lib/libgpm.so.1 Reading symbols from /lib/libncurses.so.5...done. Loaded symbols for /lib/libncurses.so.5 Reading symbols from /lib/libm.so.6...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /lib/libutil.so.1...done. Loaded symbols for /lib/libutil.so.1 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /usr/X11R6/lib/libXp.so.6...done. Loaded symbols for /usr/X11R6/lib/libXp.so.6 ---Type <return> to continue, or q <return> to quit--- Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/libnss_files.so.2...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /lib/libnss_dns.so.2...done. Loaded symbols for /lib/libnss_dns.so.2 Reading symbols from /lib/libresolv.so.2...done. Loaded symbols for /lib/libresolv.so.2 #0 0x40533861 in kill () from /lib/libc.so.6 (gdb) where #0 0x40533861 in kill () from /lib/libc.so.6 #1 0x080a9ca3 in fatal_error_signal (sig=11) at emacs.c:539 #2 <signal handler called> #3 0x402b9888 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6 #4 0x402b9bdf in xtWidgetAlloc () from /usr/X11R6/lib/libXt.so.6 #5 0x402b9dc0 in xtCreate () from /usr/X11R6/lib/libXt.so.6 #6 0x402ba71b in _XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6 #7 0x402ba7bd in XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6 #8 0x0817ad50 in x_create_widgets (f=0x8488590, lisp_window_id=136386244, parent=136386244) at frame-x.c:1957 #9 0x0817b32d in x_init_frame_1 (f=0x8488590, props=136386244) at frame-x.c:2184 #10 0x080fed6c in Fmake_frame (props=136386244, device=138360504) at frame.c:395 #11 0x080b0f1c in Ffuncall (nargs=3, args=0xbfffea58) at eval.c:3528 #12 0x0808bf79 in execute_optimized_program ( program=0x84884b8 "Æ \210Ç ?&È\fÉ \"¬\027Ê\r\013\"\022Ë\rÈ\tÌ \"＠\"\211\020\026\020Í\r!\025Î\016\021!\210Ï\211\024\207", stack_depth=5, constants_data=0x82aa4f8) at bytecode.c:746 #13 0x0808bc59 in funcall_compiled_function (fun=137261624, nargs=0, args=0xbfffeb9c) at bytecode.c:515 #14 0x080b10bf in Ffuncall (nargs=1, args=0xbfffeb98) at eval.c:3563 #15 0x0808bf79 in execute_optimized_program ( program=0x83f2f90 "\013A\035ÆÇ\032\031È\r!\025\bÉa«\004Ê \210ËÌ!«\004Í \210\f«\017\016\035¬\013ÎÏÐ\f!ÑQ! \210Ò \210*Ó \210Ô \210rÕÖ!q\210× \210ØÙ!\210\016!Úa«\005\016\" \210)Û Üa«\bÝ ¬\004Þ \210ß \210Ù\026#Ý \004àÇ!)\207moA\001", stack_depth=4, constants_data=0x8339bd0) at bytecode.c:746 #16 0x0808bc59 in funcall_compiled_function (fun=137580756, nargs=0, args=0xbfffecdc) at bytecode.c:515 #17 0x080b10bf in Ffuncall (nargs=1, args=0xbfffecd8) at eval.c:3563 #18 0x0808bf79 in execute_optimized_program ( program=0x83e1148 "\t«\005ÆÇ!\207È\021É \211\034«\025\fG\rGW«\016Ê\r!Ê\f!k«\005Ë\f!\025)Ì\r!\025Í \210Î \210\013®\aÏÐ!\002È\eÑ\016#\016$\"\022\013«\tÒÓÔ\n\"Õ\"\210\n¬\004Ö \210×\n\016%\b\016&\013%\210Ø \210)\016!¬\022\016\"«\016ÙÚÛ\016'!\016\"\"ÜÈ#\210\016!¬\023\b¬\006Ý\016(!\210Ý\016)!\210Ý\016*!\210Þ\216ß \210)\016+\003à \207 or re¡", stack_depth=7, constants_data=0x8339a10) at bytecode.c:746 #19 0x0808bc59 in funcall_compiled_function (fun=137580700, nargs=0, args=0xbfffed84) at bytecode.c:515 #20 0x080b0832 in Feval (form=137554788) at eval.c:3388 #21 0x080b6b06 in condition_case_1 (handlers=136386340, bfun=0x80aff00 <Feval>, barg=137554788, hfun=0x8094700 <cmd_error>, harg=136386244) at eval.c:1651 #22 0x0809478f in top_level_1 (dummy=136386244) at cmdloop.c:206 #23 0x080b69cc in internal_catch (tag=136462340, func=0x8094760 <top_level_1>, arg=136386244, threw=0x0) at eval.c:1317 #24 0x08094052 in initial_command_loop (load_me=136386244) at cmdloop.c:285 #25 0x080aaacd in xemacs_21_4_5_i686_pc_linux () at emacs.c:2353 #26 0x080ac7f9 in main () at emacs.c:2782 #27 0x405227ee in __libc_start_main () from /lib/libc.so.6

3 participants
2 comments

fix for gtk-faces.el 22 years, 5 months

John Paul Wallington

I have a fix for XEmacs 21.4.5. When I built --with-gtk default faces weren't setup. If you examine gtk-faces.el in your sources, and look at: (defun gtk-init-device-faces (device) ;; ;; If the "default" face didn't have a font specified, try to pick one. ;; (if (not (eq (device-type device) 'gtk)) nil (gtk-init-pointers) '(let* ((style (gtk-style-info device)) I think the last line is the baddy: the let* shouldn't be quoted. If you just remove the ' and make install again it works. -- John Paul Wallington

2 participants
3 comments

XEmacs developer wannabe 22 years, 5 months

tony shahov

Hello, my name is Tony Shahov and I wold like to join your team, just in case you find my skills adequate. Some facts about myself. I am from Russia, St. Petersburg. I am 24. I work for Scientific and Research Institute of Electric and Physical Apparatus, Computer Tomography Laboratory as a Software Developer. I studied computer Science in Polytechnical Institute in St. Petersburg (not graduated). I have some expertise in using Linux (6 years) and some other Unices. Languages: tough C/C++ and Haskell, though I can list many more (including Lisp). Toolkits/Libraries: GTK, Qt, good overall understanding of commonly used Unix libraries. Emacs: Just common everyday usage. English: fluent, as you noticed so far. Nothing special probably, but I want to participate in a big open software project (for a great glory). Kind regards, Tony Shahov

2 participants
1 comments

http://www.xemacs.org/ improvement work results 22 years, 5 months

Adrian Aichner

The following message is a courtesy copy of an article that has been posted to comp.emacs.xemacs as well. Hi All! Some of you might be interested in how many of this links behind http://www.xemacs.org/ are broken. I was, when I set out to test and improve the situation back in September 2001. I decided to use http://www.linklint.org/ for the purpose and found this: --------------------------------------------. file: urlsum.txt | --------------------------------------------| Linklint version: 2.3.3 | | Linklink checked 734 urls: | 625 were ok, 94 failed. 72 urls moved. | 7 hosts failed: 7 urls could be retried.| 18 files had failed urls. | There were 50 files with broken links. | --------------------------------------------' After putting in some work, using Google a lot, contacting many people, and inducing many page hits along the way I can report these results as of today: --------------------------------------------. file: urlsum.txt | --------------------------------------------| Linklint version: 2.3.5 | | Linklint checked 796 urls: | 776 were ok, 7 failed. 36 urls moved. | 5 hosts failed: 5 urls could be retried.| 7 files had failed urls. | There were 14 files with broken links. | --------------------------------------------' Of these remaining problems most are caused by the dynamics of the internet. Some of our mirrors deny requests from outside their top-level domains. Some sites are not reachable 100% of the time. Best regards, Adrian -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

1 participants
0 comments

Data Capture / Entry / Coding Service. 22 years, 5 months

Mr. Neville Konkravala.

Dated: 17th, November 2001. Dear Sir / Ma'm: I came upon your email address at the following web page :- http://www.finseth.com/~fin/emacs.html Understandably you must be a very preoccupied person - so without wasting a lot of your time, let me get down straight to the purpose of this email. You see the company I am employed with specializes in the field of data or text capturing. Briefly speaking we specialize in capturing text from paper documents (or from most other mediums) and converting it into its desirous electronic equivalent. We also specialize in (and are presently the only company offering) the coding / tagging of such data in accordance to our client's uniquely specific and tailor made requirements. We consistently execute both these processes with an unsurpassed accuracy rate preceding 99.99 % which does aptly speak volumes in favor of and about the quality control standards of our services. I write this wondering if you or your company ever needs to or do outsource similar services - In which case I would appreciate hearing from you about the kind of requirements and expectations you generally have, or are desirous of availing while availing such. Once I get a brief idea of those I could and would further elaborate on the aspects of how and what we may have to offer in order to best meet your requirements or expectations, and the translated benefits of outsourcing such services from my company in comparison to other companies providing such. You can be assured that under the given circumstances it would prove not only to be very mutually beneficial for our organizations, but also a satisfactory association. I am hopeful of and look forward to your response either way. Cordial regards, Ms. Prochee Dinshaw. [Sr. Sales Manager.] For :- Konkravala & Associates.

1 participants
0 comments

[PATCH] 21.1.4-mule: auto save doubles escape chars 22 years, 5 months

Kyle Jones

This function reproduces the problem (defun show-bug () (interactive) (let ((coding-system-for-read 'no-conversion)) (find-file "/tmp/foo")) (erase-buffer) (insert "\e$BF|K\\8l\e(B\n") (save-buffer) (insert "i live\n") (do-auto-save)) Now cd to /tmp and diff /tmp/foo and its autosave file. I advise piping the result through cat -v so you can see the control characters. Each escape character in the file has been doubled. Looking at the XEmacs code, this seems to be intentional, though I don't know why. Here's a patch. Recommended for the 21.1 code line because this problem corrupts autosave files of mail folders that have ISO-2022-JP encoded messages in them. I haven't looked at the development code line so I don't know if the patch is approrpiate there. I also changed the MULE #ifdef to FILE_CODING because maintaining the current coding system looks like the right thing to do in that context also. *** src/fileio.c 2001/10/31 04:21:24 1.1 --- src/fileio.c 2001/10/31 04:22:01 *************** *** 3825,3832 **** return /* !!#### need to deal with this 'escape-quoted everywhere */ Fwrite_region_internal (Qnil, Qnil, a, Qnil, Qlambda, Qnil, ! #ifdef MULE ! Qescape_quoted #else Qnil #endif --- 3825,3832 ---- return /* !!#### need to deal with this 'escape-quoted everywhere */ Fwrite_region_internal (Qnil, Qnil, a, Qnil, Qlambda, Qnil, ! #ifdef FILE_CODING ! current_buffer->buffer_file_coding_system #else Qnil #endif

3 participants
7 comments

Installs in the wrong directory on Windows 3 22 years, 5 months

Claus Sørensen

Dear Bug Team! XEmacs installs in the wrong directory on non English versions of Windows 32 machines. The correct directory for the Danish version is "c:\Programmer" instead of "c:\Program files". You should look for the Program directory ind the Windows Registry instead of using the English version. The most enjoyable greetings ================================================================ _/ __/ | + Jeg vil leve i en verden, hvor Claus Sørensen / (_ . al kommunikation er baseret på Nøddelunden 110 | _} _ frie og åbne standarder, så 2765 Smørum ( |_o `)(| ) enhver har friheden til at cs(a)chbs.dk \ /(_)-(_ (' vælge. 20 94 62 34 |__\o./ _><o . Claus Sørensen, 2001 http://www.chbs.dk '--|' []

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 November 2001