21.2 Showstopper? Warning: BAD DATA LOSS on disk full
23 years, 2 months
Stephen J. Turnbull
Stephen J. Turnbull
I've discovered that in this XEmacs, if a file is truncated due to
lack of disk space on write, XEmacs blithely goes ahead and renames
the tmp file and does whatever it usually does (including remove) to
the previous version.
Verified with
rm test; touch test # dunno if this is needed
/playpen/src/Builds/XEmacs-21.2/src/xemacs -no-autoloads
C-x C-f test
C-x i file-bigger-than-available-space
C-x C-s
C-x C-x
and df says no remaining space, and diff says test ==
head(file-bigger-than-available-space).
This is not a problem of the OS (Linux 2.2.18pre2, Debian unstable,
glibc 2.2.1 (Debian rev 1)) per se AFAICT; cp fills up the partition,
as expected, but then gives an error return.
Gotta go back and grade entrance exams, will investigate further
later, but this is a bad one. Have no idea when this happened, I'd
been using 21.1 for mail & stuff until this install, and havn't seen
disk full in my devel directories for many months.
Approx. 21.2.42, CVS current as of approximately Jan 28 9:00 UTC.
uname -a: Linux turnbull 2.2.18pre2 #1 Mon Sep 4 19:28:49 JST 2000 i586 unknown
/coda/Projects/XEmacs/21.2-HEAD/configure '--srcdir=/coda/Projects/XEmacs/21.2-HEAD' '--prefix=/playpen/gnu' '--exec-prefix=/playpen/gnu/plat' '--with-mule' '--with-xim=xlib' '--with-xfs'
XEmacs 21.2-b42 "Poseidon" configured for `i586-pc-linux'.
Compilation / Installation:
Source code location: /coda/Projects/XEmacs/21.2-HEAD
Installation prefix: /playpen/gnu
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -g -O3 -Wall -Wno-switch -Wpointer-arith -Winline -Wmissing-prototypes -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/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw
- Athena library to link: Xaw
Using Lucid menubars.
Using Lucid scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
TTY:
Compiling in support for ncurses.
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:
Compiling in support for Berkeley database.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
- Using XFontSet to provide bilingual menubar.
Compiling in support for Canna on Mule.
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Compiling in support for dynamic shared object modules.
Compiling in support for extra debugging code.
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: ---------------------------------------------------------
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
- 6 participants
- 12 comments
JDE still won't build.
23 years, 2 months
Steve Youngs
Steve Youngs
cd ./prog/jde
make distclean
make autoloads
make bindist
And I get:
cd /home/steve/test-it/build/pkg-build/prog/jde/
make bindist
xemacs -no-autoloads -batch -l /home/steve/test-it/build/pkg-build/package-compile.el -- jde cc-mode semantic debug speedbar edit-utils eterm mail-lib xemacs-base eieio elib senator -- lisp/auto-autoloads.el
Loading /usr/local/lib/xemacs-21.2-b44/lisp/auto-autoloads...
Wrong type argument: stringp, nil
xemacs exiting
.
make: *** [lisp/auto-autoloads.elc] Error 255
Compilation exited abnormally with code 2 at Mon Feb 19 10:58:28
This is with the inclusion to the new Eieio package and Jan's patch to
Semantic.
Could somebody please help Paul to fix this? Jan perhaps, if you can
spare the time? I'd really appreciate it.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
- 2 participants
- 1 comments
font-lock still not right. :-(
23 years, 2 months
Steve Youngs
Steve Youngs
Sorry Matt, but I think there is still something wrong with font-lock.
When starting XEmacs, the little progress meter that says "Fontifying
World" tells me "Fontifying Aborted...".
And if you eval the following:
-----------
(defun world-mode ()
"eicq resource file mode.
Quick hack for font-lock. Each record is separated by \"==== \" at the
beginning of the line."
(interactive)
(kill-all-local-variables)
(setq mode-name "world")
(setq major-mode 'world-mode)
(setq fill-column 100)
(auto-fill-mode 1)
;; hiding details for privacy
(outline-minor-mode)
(set (make-local-variable 'outline-regexp)
"==== ")
;; highlight this month and next month
;; format example: "^Aug 08, 1979$"
(let* ((this-month (string-to-number (format-time-string "%m")))
(this-month-name (aref eicq-monthnames this-month))
(next-month-name (aref eicq-monthnames (1+ this-month)))
(month-regexp (format "^%s.*\\|^%s.*"
this-month-name next-month-name)))
(setq font-lock-keywords
;; highlight separator
`(("^==== " (0 'font-lock-warning-face t))
;; highlight date
(,month-regexp (0 'highlight t))
;; highlight keyword prefixed with :
(":\\(\\w\\|-\\)+" 0 font-lock-reference-face t))))
(font-lock-mode 1))
------------
And then:
M-x world-mode
It gives:
Wrong type argument: markerp, nil
With this backtrace:
# bind (standard-output stack-trace-on-signal debug-on-signal stack-trace-on-error debug-on-error)
marker-position(nil)
# bind (loudly end start)
font-lock-fontify-syntactically-region(1 531 nil)
# (unwind-protect ...)
# bind (modified buffer-undo-list inhibit-read-only old-syntax-table buffer-file-name buffer-file-truename loudly end beg)
font-lock-default-fontify-region(1 531 nil)
# bind (loudly end beg)
font-lock-fontify-region(1 531)
# (unwind-protect ...)
# bind (match-data)
# (unwind-protect ...)
# bind (message verbose end start buffer)
lazy-shot-fontify-internal(#<buffer "world"> 1 531 t "")
# bind (start end buffer stealth extent)
lazy-shot-lock-extent(#<destroyed extent> nil)
# bind (extent)
lazy-shot-redisplay-function(#<destroyed extent>)
# (condition-case ... . error)
# (catch top-level ...)
That code snippet above (world-mode) works fine with the old, pre
syntax-table font-lock.el.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
- 2 participants
- 2 comments
core dump doing practically anything to region.
23 years, 2 months
Steve Youngs
Steve Youngs
This one is _really_ annoying.
I'm getting core dumps anytime I do something to a region.
Recipe for crash:
C-SPC
move point somewhere to create a region
C-w (M-w works just as well, even M-x boxquote-region)
CRASH!
Okay, I don't know anything about gdb (never been inspired enough to
learn), but here's what I've been able to dredge up. I apologise if
it's not useful.
Current directory is /usr/local/bin/
GNU gdb 5.0
Copyright 2000 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-slackware-linux"...
(gdb) core-file ~/core
warning: core file may not match specified executable file.
Core was generated by `xemacs'.
Program terminated with signal 6, Aborted.
Cannot access memory at address 0x40018e30
#0 0x403322e1 in ?? ()
(gdb) Starting program: /usr/local/bin/xemacs-21.2-b44
Cannot access memory at address 0x40018e30
(gdb) Continuing.
Cannot access memory at address 0x40018e30
(gdb) Continuing.
Fatal error: assertion failed, file lisp.h, line 1397, RECORD_TYPEP (obj, lrecord_type_marker)
Program received signal SIGABRT, Aborted.
0x403322e1 in __kill () from /lib/libc.so.6
(gdb) Continuing.
Fatal error (6).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, 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/bin/xemacs-21.2-b44 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:
call-interactively(kill-region)
# (condition-case ... . error)
# (catch top-level ...)
Program received signal SIGABRT, Aborted.
0x403322e1 in __kill () from /lib/libc.so.6
(gdb) Continuing.
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb)
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
- 2 participants
- 2 comments
Crash when entering Info reader
23 years, 2 months
Evgeny Roubinchtein
Evgeny Roubinchtein
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.2 (beta44) "Thalia" [Lucid] (i386-unknown-freebsd4.2, Mule) of Sun Feb 18 2001 on ruby.localdomain
configured using `configure --with-mule --site-includes=/usr/local/include --site-libraries=/usr/local/lib'
I did a "cvs -up -r release-21-2 this morning."
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
xemacs -vanilla
C-h i
Kaboom!
Lisp backtrace follows:
re-search-forward("^\\* \\([^: \n]*\\):?:[ \n]" nil t)
# bind (case-fold-search xref-regexp)
# (unwind-protect ...)
Info-fontify-node()
# bind (active-expression)
# (unwind-protect ...)
Info-select-node()
# bind (found guesspos regexp qnode)
# (unwind-protect ...)
# bind (line tryfile no-going-back nodename filename)
Info-find-file-node("/usr/local/xemacs/beta/i386-unknown-freebsd4.2/info/dir" "top" nil nil nil)
# bind (line tryfile no-going-back nodename filename)
Info-find-node("dir" "top")
Info-directory()
# bind (file)
#<compiled-function (&optional file) "...(82)" [command-line-args-left command-line-args Info-standalone file p string-match "^-[fe]" "info" t 3 "^-" 2 nil (...) Info-goto-node "(" ")" get-buffer "*info*" switch-to-buffer Info-directory] 5 ("/usr/local/xemacs/beta/i386-unknown-freebsd4.2/lisp/info.elc" . 9548) (byte-code ÁÂÃÄ$C" [current-prefix-arg read-file-name "Info file name: " nil t] 5)>()
call-interactively(info)
# (condition-case ... . error)
# (catch top-level ...)
Abort trap (core dumped)
And here's gdb stack trace:
#0 0x287593c8 in kill () from /usr/lib/libc.so.4
#1 0x80bc127 in fatal_error_signal (sig=6) at /usr/local/xemacs/beta/src/emacs.c:535
#2 0xbfbfffac in ?? ()
#3 0x80bf165 in assert_failed (file=0x828bb00 "/usr/local/xemacs/beta/src/insdel.c",
line=1122, expr=0x828b2cf "VALID_BYTIND_P (buf, x)")
at /usr/local/xemacs/beta/src/emacs.c:3214
#4 0x817ad44 in bytind_to_bufpos (buf=0x83a1a00, x=4771)
at /usr/local/xemacs/beta/src/insdel.c:1122
#5 0x81c49e4 in re_search_2 (bufp=0x82d7ca0,
str1=0x287d63b2 "File: dir\tNode: Top\tThis is the top of the INFO tree\n\n This is Info, the online documentation browsing system.\n This page (the Directory node) gives a menu of major topics.\n\n button1 or button2 on "..., size1=11128,
str2=0x287d9b20 "", size2=0, startpos=4770, range=6358, regs=0x82d91b4, stop=11128)
at /usr/local/xemacs/beta/src/regex.c:4050
#6 0x81ccb81 in search_buffer (buf=0x83a1a00, string=141856388, bufpos=5685,
buflim=12043, n=1, RE=1, trt=139626496, inverse_trt=139628544, posix=0)
at /usr/local/xemacs/beta/src/search.c:1221
#7 0x81cc63e in search_command (string=141856388, limit=137390084, noerror=137390108,
count=137390084, buffer=137390084, direction=1, RE=1, posix=0)
at /usr/local/xemacs/beta/src/search.c:1051
#8 0x81d14c4 in Fre_search_forward (regexp=141856388, limit=137390084,
noerror=137390108, count=137390084, buffer=137390084)
at /usr/local/xemacs/beta/src/search.c:2144
#9 0x80c5585 in Ffuncall (nargs=4, args=0xbfbfe878)
at /usr/local/xemacs/beta/src/eval.c:3528
#10 0x8093ff9 in execute_optimized_program (
program=0x879b910 "\212ÆÇÈ\b!ÉQ\031\036(ÊËpedÌ%\210ÍÎ!\210ÌÏÌe\034\e\035\032eb\210ÐÑÌÆ#\210`eZ\025Òe`\"\022Ó\nÔÆ#\210\013¬4\fb\210Ì\177\210i\rÕ\\W«\006Æ\211\023ªí\fb\210\rÖ\\u\210×ØÌÆ#\210Ùu\210Úc\210Û \210ÜÙ!\210`\024Ï\025ªË,ÍÙ!\210eb\210ÝÞ!«\030Ï\225b\210Ýß!«\017Ï\225b\210àÙ\224Ù\225á#\210ªîeb\210Ð\tÌÆ#«\023Ï\224SfâU¬òàÙ\224Ù\225á#\210ªèeb\210ãäÌÆ#«\022ÐåÌÆ#«\013àÙ\224Ù\225æ#\210ªð"..., stack_depth=7, constants_data=0x8785e10)
at /usr/local/xemacs/beta/src/bytecode.c:746
#11 0x8093c22 in funcall_compiled_function (fun=142147444, nargs=0, args=0xbfbfe9cc)
at /usr/local/xemacs/beta/src/bytecode.c:518
#12 0x80c56bb in Ffuncall (nargs=1, args=0xbfbfe9c8)
at /usr/local/xemacs/beta/src/eval.c:3563
#13 0x8093ff9 in execute_optimized_program (
program=0x879bb10 "~\210\212ÆÇ!\210Èy\210ÉÊ!\210`ËÌw\210`{\022Í \210Îy\210Ì\035`ÉÏÌÐ#«\022`SÑÒ!«\fÎ\225b\210Óp!\025ª\002d}\210\fÔk¬ eb\210ÌÕ Ð\031\e\030ÉÖÌÐ#«\n×Ø\fÙQ!\210ªñÚ\013!\210+Û \210\016 «\004Ü \210ÝÞ!\210\016!\004ß\r!*\207ou start off looking at that node,\nwhich is (dir\016\217©\036\017\201Ð\217¸\201«\217§\201Ñ \217©\026\017\201ª\217¢\016\017\016\016\201®\217¤\201Ò\016"..., stack_depth=5, constants_data=0x8721e10)
at /usr/local/xemacs/beta/src/bytecode.c:746
#14 0x8093c22 in funcall_compiled_function (fun=142145596, nargs=0, args=0xbfbfeb1c)
at /usr/local/xemacs/beta/src/bytecode.c:518
#15 0x80c56bb in Ffuncall (nargs=1, args=0xbfbfeb18)
at /usr/local/xemacs/beta/src/eval.c:3563
#16 0x8093ff9 in execute_optimized_program (
program=0x876be10 "\tÆa¬\005ÇÈ!\210Ép!\210ÊË!\210\tÆa¬\004Æ \210\f«$\r\fk¬\037\016D«\eÌ\r!Í\230¬\024ÎÏÐÌ\r!\"!«\aÑÒ!\210ª\004Ó \210\r«\f\016E¬\bÔ\r\0169`#\210~\210Õ\211\0269\026FÖ\216\f\203\233", stack_depth=6, constants_data=0x876b410)
at /usr/local/xemacs/beta/src/bytecode.c:746
#17 0x8093c22 in funcall_compiled_function (fun=139158964, nargs=5, args=0xbfbfec6c)
at /usr/local/xemacs/beta/src/bytecode.c:518
#18 0x80c56bb in Ffuncall (nargs=6, args=0xbfbfec68)
at /usr/local/xemacs/beta/src/eval.c:3563
#19 0x8093ff9 in execute_optimized_program (
program=0x8785c10 "Æ \210\r¬\fÇÈ\b\016\030\016\031\016\032%\207É\r!È\211\034\031\eÊË\013\"«\006\016\035Cª\027Ì\013!«\004ͪ\017\016\e«\tÎ\016\034\016\e\"ª\003\016\034\211\032«\024\f¬\021Ï\013\n＠\"\021Ð\t!\024\nA\211\022¬î\f\006Ï\f!\025Ñ,«\fÇ\r\b\016\030\016\031\016\032%\207ÊÒ\r\"«\016ÓÔ!«\005Ô\r!\207ÕÖ!\207Õ×\r\"\207\bî\002", stack_depth=7,
constants_data=0x8721b10) at /usr/local/xemacs/beta/src/bytecode.c:746
#20 0x8093c22 in funcall_compiled_function (fun=139158936, nargs=2, args=0xbfbfedbc)
at /usr/local/xemacs/beta/src/bytecode.c:518
#21 0x80c56bb in Ffuncall (nargs=3, args=0xbfbfedb8)
at /usr/local/xemacs/beta/src/eval.c:3563
#22 0x8093ff9 in execute_optimized_program (program=0x8718770 "ÀÁÂ\"\207",
stack_depth=3, constants_data=0x8676330)
at /usr/local/xemacs/beta/src/bytecode.c:746
#23 0x8093c22 in funcall_compiled_function (fun=142146100, nargs=0, args=0xbfbfeefc)
at /usr/local/xemacs/beta/src/bytecode.c:518
#24 0x80c56bb in Ffuncall (nargs=1, args=0xbfbfeef8)
at /usr/local/xemacs/beta/src/eval.c:3563
#25 0x8093ff9 in execute_optimized_program (
program=0x8771a10 "\t\211\034«4ÅÆ\f＠\"«'\fA＠Çk« \n¬\035È\211\022«\030\fGÉU«\022ÅÊË\f8\"¬\nË\f8\211\023«\003Ì\020\fA\211\024¬Î)\013«\013Í\216ÎÏ\013ÐQ!)\207ÑÒ!«\005ÓÒ!\207Ô \207", stack_depth=5, constants_data=0x877fe90)
at /usr/local/xemacs/beta/src/bytecode.c:746
#26 0x8093c22 in funcall_compiled_function (fun=139158852, nargs=0, args=0xbfbff078)
at /usr/local/xemacs/beta/src/bytecode.c:518
#27 0x80c56bb in Ffuncall (nargs=1, args=0xbfbff074)
at /usr/local/xemacs/beta/src/eval.c:3563
#28 0x80ca963 in apply1 (fn=139158852, arg=137390084)
at /usr/local/xemacs/beta/src/eval.c:4152
#29 0x8098141 in Fcall_interactively (function=137517708, record_flag=137390084,
keys=137390084) at /usr/local/xemacs/beta/src/callint.c:397
#30 0x80c3d10 in Fcommand_execute (cmd=137517708, record_flag=137390084,
keys=137390084) at /usr/local/xemacs/beta/src/eval.c:2970
#31 0x8118b8d in execute_command_event (command_builder=0x865a840, event=141478472)
at /usr/local/xemacs/beta/src/event-stream.c:3834
#32 0x81197e0 in Fdispatch_event (event=141478472)
at /usr/local/xemacs/beta/src/event-stream.c:4165
#33 0x80a352a in Fcommand_loop_1 () at /usr/local/xemacs/beta/src/cmdloop.c:583
#34 0x80a37b2 in command_loop_1 (dummy=137390084)
at /usr/local/xemacs/beta/src/cmdloop.c:494
#35 0x80cb4c5 in condition_case_1 (handlers=137390180,
bfun=0x80a3774 <command_loop_1>, barg=137390084, hfun=0x80a3824 <cmd_error>,
harg=137390084) at /usr/local/xemacs/beta/src/eval.c:1651
#36 0x80a3913 in command_loop_2 (dummy=137390084)
at /usr/local/xemacs/beta/src/cmdloop.c:256
#37 0x80cb3c4 in internal_catch (tag=137470412, func=0x80a38d8 <command_loop_2>,
arg=137390084, threw=0x0) at /usr/local/xemacs/beta/src/eval.c:1317
#38 0x80a2d9a in initial_command_loop (load_me=137390084)
at /usr/local/xemacs/beta/src/cmdloop.c:305
#39 0x80bd4a7 in xemacs_21_2_b44_i386_unknown_freebsd4_2 (argc=2, argv=0xbfbff5c0,
envp=0xbfbff5cc, restart=0) at /usr/local/xemacs/beta/src/emacs.c:2253
#40 0x80bf3cd in main (argc=2, argv=0xbfbff5c0, envp=0xbfbff5cc)
at /usr/local/xemacs/beta/src/emacs.c:2682
#41 0x808142d in _start ()
Recent keystrokes:
n d - p r C-m C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-p C-p RET C-n C-n C-n C-n C-x 1 C-h h C-x k C-m C-h
? ? C-g C-h ? ? SPC SPC C-m M-x s u b TAB C-h a b u
g C-m C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-h a C-g C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-m C-e C-a RET C-x 1 M-x
r e p TAB o TAB r TAB C-m
Recent messages (most recent first):
Loading lazy-lock...done
Loading lazy-lock...
Loading gnus-ems...done
Loading gnus-xmas...done
Loading gnus-xmas...
Loading gnus-ems...
Parsing /home/evgeny/.mailrc... done
Parsing /home/evgeny/.mail_aliases... done
Parsing /home/evgeny/.mail_aliases...
Parsing /home/evgeny/.mailrc...
Here's
(describe-installation)
"uname -a: FreeBSD ruby.localdomain 4.2-STABLE FreeBSD 4.2-STABLE #0: Fri Jan 19 03:33:58 PST 2001 evgeny＠ruby.localdomain:/usr/src/sys/compile/RUBY i386
../configure '--with-mule' '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib'
XEmacs 21.2-b44 \"Thalia\" configured for `i386-unknown-freebsd4.2'.
Compilation / Installation:
Source code location: /usr/local/xemacs/beta
Installation prefix: /usr/local
Additional header files: /usr/local/include
Additional libraries: /usr/local/lib
Runtime library search path: /usr/local/lib:/usr/X11R6/lib
Operating system description file: `s/freebsd.h'
Machine description file: `m/intel386.h'
Compiler: gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wshadow -Wpointer-arith
Relocating allocator for buffers: yes
GNU version of malloc: yes
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/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.
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).
Compiling in support for ESD (Enlightened Sound Daemon).
Databases:
Compiling in support for Berkeley database.
Compiling in support for GNU DBM.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using Motif to provide XIM support.
Mail:
Compiling in support for \"flock\" mail spool file locking method.
Other Features:
Compiling in support for dynamic shared object modules.
Compiling in support for extra debugging code.
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: ---------------------------------------------------------
"
Thanks
--
Evgeny
AG: Add Gibberish
- 3 participants
- 2 comments
coredump when killing region
23 years, 2 months
Michael Harnois
Michael Harnois
For the last couple of days, any attempt to kill a region has resulted
in a coredump:
Current directory is /usr/local/src/xemacs-build/src/
GNU gdb 4.18
Copyright 1998 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-unknown-freebsd"...
Core was generated by `xemacs'.
Program terminated with signal 10, Bus error.
Reading symbols from /usr/X11R6/lib/libXaw.so.7...done.
Reading symbols from /usr/local/lib/libtiff.so.4...done.
Reading symbols from /usr/local/lib/libpng.so.4...done.
Reading symbols from /usr/local/lib/libjpeg.so.9...done.
Reading symbols from /usr/X11R6/lib/libXpm.so.4...done.
Reading symbols from /usr/X11R6/lib/libXmu.so.6...done.
Reading symbols from /usr/X11R6/lib/libXt.so.6...done.
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Reading symbols from /usr/X11R6/lib/libSM.so.6...done.
Reading symbols from /usr/X11R6/lib/libICE.so.6...done.
Reading symbols from /usr/local/lib/libgdbm.so.2...done.
Reading symbols from /usr/lib/libncurses.so.5...done.
Reading symbols from /usr/local/lib/libesd.so.2...done.
Reading symbols from /usr/local/lib/libaudiofile.so.0...done.
Reading symbols from /usr/lib/libm.so.2...done.
Reading symbols from /usr/local/lib/libintl.so.1...done.
Reading symbols from /usr/local/lib/libldap.so.1...done.
Reading symbols from /usr/local/lib/liblber.so.1...done.
Reading symbols from /usr/lib/libutil.so.3...done.
Reading symbols from /usr/lib/libxpg4.so.3...done.
Reading symbols from /usr/lib/libc.so.5...done.
Reading symbols from /usr/lib/libz.so.2...done.
Reading symbols from /usr/X11R6/lib/libXThrStub.so.6...done.
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0 0x28578884 in kill () from /usr/lib/libc.so.5
(gdb) where
#0 0x28578884 in kill () from /usr/lib/libc.so.5
#1 0x80b04b7 in fatal_error_signal (sig=10)
at /usr/local/src/xemacs-21.2/src/emacs.c:535
#2 0xbfbfffac in ?? ()
#3 0x80931de in Fcall_interactively (function={...}, record_flag={...},
keys={...}) at /usr/local/src/xemacs-21.2/src/callint.c:936
#4 0x80b6df3 in Fcommand_execute (cmd={...}, record_flag={...}, keys={...})
at /usr/local/src/xemacs-21.2/src/eval.c:2970
#5 0x80f9839 in execute_command_event (command_builder=0x8599540, event={...})
at /usr/local/src/xemacs-21.2/src/event-stream.c:3834
#6 0x80f9eb1 in Fdispatch_event (event={...})
at /usr/local/src/xemacs-21.2/src/event-stream.c:4165
#7 0x8099b7c in Fcommand_loop_1 ()
at /usr/local/src/xemacs-21.2/src/cmdloop.c:583
#8 0x8099df5 in command_loop_1 (dummy={...})
at /usr/local/src/xemacs-21.2/src/cmdloop.c:494
#9 0x80bd482 in condition_case_1 (handlers={...},
bfun=0x8099ddc <command_loop_1>, barg={...}, hfun=0x8099e6c <cmd_error>,
harg={...}) at /usr/local/src/xemacs-21.2/src/eval.c:1651
#10 0x8099f63 in command_loop_2 (dummy={...})
at /usr/local/src/xemacs-21.2/src/cmdloop.c:256
#11 0x80bd388 in internal_catch (tag={...}, func=0x8099f28 <command_loop_2>,
arg={...}, threw=0x0) at /usr/local/src/xemacs-21.2/src/eval.c:1317
#12 0x80998b6 in initial_command_loop (load_me={...})
at /usr/local/src/xemacs-21.2/src/cmdloop.c:305
#13 0x80b1969 in xemacs_21_2_b44_i386_unknown_freebsd5_0 (argc=3,
argv=0xbfbffcbc, envp=0xbfbffccc, restart=0)
at /usr/local/src/xemacs-21.2/src/emacs.c:2253
#14 0x80b37d9 in main (argc=3, argv=0xbfbffcbc, envp=0xbfbffccc)
at /usr/local/src/xemacs-21.2/src/emacs.c:2682
#15 0x8081175 in _start ()
(gdb)
--
Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA
mdharnois(a)home.com aa0bt(a)aa0bt.ampr.org
CYNIC, n. A blackguard whose faulty vision sees things as they are,
not as they ought to be. -- Ambrose Bierce
- 1 participants
- 0 comments
Re: vc killed my work
23 years, 2 months
Neal D. Becker
Neal D. Becker
I think I saw the same thing. I twice lost my work. I had a buffer
(c++ code) that was not under version control. I hit C-x v i. xemacs
did NOT notice it was now under vc (no update of modeline). I
reported this previously.
Later, I lost all my changes. I think I hit C-x C-q, but I'm not
certain. This has happened twice within the last week.
-- loaded from "/usr/src/bs/BUILD/xemacs-21.1.14/lisp/version.el"
Value: "21.1 (patch 14) \"Cuyahoga Valley\" XEmacs Lucid"
- 1 participants
- 0 comments
Updated packages in Pre-Releases - Feb 18
23 years, 2 months
Steve Youngs
Steve Youngs
The following packages have been updated and are in the Pre-Releases
directory:
PLEASE NOTE: These are the _ONLY_ packages in the Pre-Releases
directory.
edit-utils-1.56-pkg.tar.gz
--------------------------
2001-02-16 Martin Buchholz <martin(a)xemacs.org>
* lazy-lock.el (lazy-lock-pre-idle-fontify-windows):
Avoid infinite loop if selected frame is not visible.
* lazy-lock.el (lazy-lock-maybe-fontify-window):
Can't use with-selected-window - not in 21.1.
2001-02-15 Martin Buchholz <martin(a)xemacs.org>
Fix bug:
xemacs -q -no-site-file ~/.emacs -f font-lock-mode \
-f turn-on-lazy-lock -f split-window-vertically -f make-frame
Then select upper window, move mouse to single-window frame, move
mouse back to split-window frame. Selected window will be lower one.
* lazy-lock.el:
(lazy-lock-pre-idle-fontify-windows):
The idiom (with-selected-window x ...) only works if x is in the
same frame as the selected window - else the frame-selected window
of x's frame is not restored.
(lazy-lock-maybe-fontify-frame): New.
eieio-1.00-pkg.tar.gz
---------------------
This is a NEW package. From the info file:
EIEIO is a framework for writing object oriented applications in
emacs lisp, and is a result of my taking various object oriented
classes at work and my attempt to understand some of it better by
implementing it. The real reason I started eieio is because someone in
one of my classes said "I bet emacs can't do that!". Well then, I just
had to prove them wrong!
gnus-1.55-pkg.tar.gz
--------------------
2001-02-14 Steve Youngs <youngs(a)xemacs.org>
* gnus-win.el: (gnus-configure-windows). Use 'switch-to-buffer' instead
of 'set-buffer' if featurep 'xemacs.
(gnus-remove-some-windows): Ditto.
ilisp-1.15-pkg.tar.gz
---------------------
Updates to the Makefile.
prog-modes-1.33-pkg.tar.gz
--------------------------
2001-02-10 Matt Tucker <tuck(a)whistlingfish.net>
* cperl-mode.el (cperl-mode): Disable override of
font-lock-unfontify-region-function under XEmacs
vhdl-1.13-pkg.tar.gz
--------------------
2001-02-16 Steve Youngs <youngs(a)xemacs.org>
* Sync with version 3.31.20.
Installing them:
===============
21.1
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3) Select any or all of the above packages (instructions at end of
*PACKAGES* buffer).
4) Packages -> Install/Remove Selected
5) Restart XEmacs.
21.2
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3 - 5) As per 21.1.
As usual, let me know if anyting goes belly up.
--
|---<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
Re: 21.2.44 crash on Solaris 2.7
23 years, 2 months
Jan Vroonhof
Jan Vroonhof
Raymond Toy <toy(a)rtp.ericsson.se> writes:
> 2001-02-16 Raymond Toy <toy(a)rtp.ericsson.se>
>
> * lwlib-Xaw.c: Always include ATHENA_AsciiText_h_ to get the
> text-field widget.
> (xaw_creation_table): Always include the text-field widget
Looks fine. I missed this when reading my review mailbox so I am not
sure somebody didn't already reply.
I will apply this tomorrow.
Jan
- 1 participants
- 0 comments
syntax-table / autoload issues
23 years, 2 months
Matt Tucker
Matt Tucker
The new syntax-table capabalities which were recently committed broke
autoload.el. Specifically, it was choking with "Unbalanced parentheses"
on files which contained unquoted pipe ('|') characters.
I've managed to figure out what was happening, and have a fix for it
which I'll be submitting. I wanted to discuss the issue a bit though,
and get someone's opinion on the right thing to do.
The problem is that lisp-mode-syntax-table was being incorrectly
initialized because the length of the list returned by
parse-partial-sexp changed (from 8 to 10) with the new functionality.
lisp-mode-syntax-table is copied from emacs-lisp-mode-syntax-table. It
then (among other things) gets | defined as a quote character. Then if
"new" parse-partial-sexp functionality is available, | is redefined as
punctuation and as part of the #|...|# comment sequence.
Here's the fix (and I realize that these diffs may be a bit mangled by
the text wrapping of my mail client. sorry about that, and I'll make
sure the final one sent to xemacs-patches isn't):
Index: lisp-mode.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/lisp-mode.el,v
retrieving revision 1.10.2.7
diff -u -r1.10.2.7 lisp-mode.el
--- lisp-mode.el 2000/11/23 06:27:36 1.10.2.7
+++ lisp-mode.el 2001/02/17 09:34:25
＠＠ -177,7 +177,7 ＠＠
;;
;; If emacs was compiled with NEW_SYNTAX, then do
;; CL's #| |# block comments.
- (if (= 8 (length (parse-partial-sexp (point) (point))))
+ (if (< 7 (length (parse-partial-sexp (point) (point))))
(progn
(modify-syntax-entry ?# "' 58"
lisp-mode-syntax-table)
(modify-syntax-entry ?| ". 67"
lisp-mode-syntax-table))
---- end of patch ----
I have three problems with this as the only fix, though:
1) This seeems like an odd way to detect syntax-table functionality,
and XEmacs now supports the required functionality unequivocally,
so there's no need to detect it at all.
2) | should still be a quote character under lisp-mode, in addition
to being part of a two-char comment sequence.
3) autoload.el should be using the emacs-lisp syntax table, instead of
the standard lisp one (it is, after all, dealing with emacs lisp).
Therefore, I propose the following patch instead:
Index: lisp-mode.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/lisp-mode.el,v
retrieving revision 1.10.2.7
diff -u -r1.10.2.7 lisp-mode.el
--- lisp-mode.el 2000/11/23 06:27:36 1.10.2.7
+++ lisp-mode.el 2001/02/17 09:45:14
＠＠ -170,19 +170,11 ＠＠
(if (not lisp-mode-syntax-table)
(progn (setq lisp-mode-syntax-table
(copy-syntax-table emacs-lisp-mode-syntax-table))
- (modify-syntax-entry ?\| "\" " lisp-mode-syntax-table)
(modify-syntax-entry ?\[ "_ " lisp-mode-syntax-table)
;; XEmacs changes
(modify-syntax-entry ?\] "_ " lisp-mode-syntax-table)
- ;;
- ;; If emacs was compiled with NEW_SYNTAX, then do
- ;; CL's #| |# block comments.
- (if (= 8 (length (parse-partial-sexp (point) (point))))
- (progn
- (modify-syntax-entry ?# "' 58"
lisp-mode-syntax-table)
- (modify-syntax-entry ?| ". 67"
lisp-mode-syntax-table))
- ;; else, old style
- (modify-syntax-entry ?\| "\" " lisp-mode-syntax-table))))
+ (modify-syntax-entry ?# "' 58" lisp-mode-syntax-table)
+ (modify-syntax-entry ?| "\" 67" lisp-mode-syntax-table)))
(define-abbrev-table 'lisp-mode-abbrev-table ())
Index: autoload.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/autoload.el,v
retrieving revision 1.2.2.7
diff -u -r1.2.2.7 autoload.el
--- autoload.el 2000/09/20 02:39:08 1.2.2.7
+++ autoload.el 2001/02/17 09:45:14
＠＠ -167,7 +167,7 ＠＠
(let ((find-file-hooks nil)
(enable-local-variables nil))
(set-buffer (or visited (find-file-noselect file)))
- (set-syntax-table lisp-mode-syntax-table))
+ (set-syntax-table emacs-lisp-mode-syntax-table))
(save-excursion
(save-restriction
(widen)
This fixes both autoload.el and lisp-mode-syntax-table properly. Any
objections?
- 2 participants
- 1 comments