December 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: XEmacs 21.2.23 crashes when url-insert-file-contents 25 years, 1 month

Hrvoje Niksic

Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: > Now we call report_extent_modification which calls > > map_extents(from = 7, to = 8, fn = 0x1cd3f8,...) > > but 7 and 8 are now outside the buffer range, therefore triggering > the assert when converting them to byteinds. Fixing this is not trivial, but it's certainly possible. You can avoid the crash by clipping (from, to) to legal buffer positions, but the right fix should be to completely re-validate from and to. The same bug happens when you call more than one before/after-change function. We should hold an extent (or two markers) over the changed region, and update FROM and TO as needed. I started to do this once, but I didn't understand code in insdel.c all that well, so the multiple-change stuff swamped me. I think I'll try again soon.

2 participants
1 comments

Re: Bold and Italic fonts 25 years, 1 month

Jan Vroonhof

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > Jan, what is current status on Custom and faces? Basically, everything that I wanted to do make customize specifier friendly is done _except_ for the size stuff. (There needs to be a make-face-size function that calls frob-face-property along the lines of make-face-bold). After that it would be time to try to implement a real dynamic font model, but that is probably for 21.4 or so.. Jan

1 participants
0 comments

FAQ updated on the web site 25 years, 1 month

Sandra Wambold

Interested parties will be able to see that the XEmacs FAQ has now been updated on the web site. While the XEmacs FAQ is still woefully in need of change, what minor changes I have made are now available. Changes visible: * Content changes previously found in the CVS sources * the index.html is now index.convert, placing that page under genpage and giving it the "site look". * the Postscript versions of the FAQ have been removed. I'll probably put them back later (I don't feel like tangling with LaTeX tonight) * the many-part text version has been removed. I don't see much use for it. Priority now returns to updating the content since I have my update scheme worked out. -sew

1 participants
0 comments

21.2.24 Crashes! 25 years, 1 month

ShengHuo ZHU

When I run this code (a simplified version), XEmacs crashes. The problem is the text property. (defun test-decode (word) (let ((i -1) (s (substring word 0)) v) (while (< (incf i) (length s)) (if (eq (setq v (aref s i)) ? ) nil (aset s i (+ 128 v)))) s)) (let ((s "~{<:Ky2;S{#,NpJ)l6HK!#~}")) (put-text-property 0 (length s) 'face 'bold s) (setq s (test-decode s)) (decode-coding-string s 'cn-gb-2312)) -- Shenghuo

1 participants
0 comments

Re: XEmacs 21.2.23 crashes when url-insert-file-contents 25 years, 1 month

Hrvoje Niksic

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Gunnar Evermann writes: > > any suggestions for a fix? > > Modifications to the current buffer should be disallowed inside the > before-/after- change functions, if we hope to have any consistency > in the system. This discussion sounds familiar. And again, I disagree with your position. There are legitimate uses for changing the buffer from within the before-/after- change functions, and custom has demonstrated that. > We can fix the crash, but things like font-lock and setnu-mode, > which rely on having access to every change to operate correctly, > are still going to be screwed unless we disallow these changes. Neither font-lock nor setnu are very useful with things like Customize buffers. Maybe we should just say in the documentation that changing buffer text from after-change-functions is a bad idea for that kind of code.

2 participants
1 comments

Re: XEmacs 21.2.23 crashes when url-insert-file-contents 25 years, 1 month

Jan Vroonhof

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Modifications to the current buffer should be disallowed inside the > before-/after- change functions, if we hope to have any consistency > in the system. We can fix the crash, but things like font-lock and Are you suggesting temporarily making the buffer read-only, or disallowing them "by policy"? Jan

2 participants
1 comments

Bold and Italic fonts 25 years, 1 month

claudia.yastremiz＠barclayscapital.com

Dear All, I have found that between XEmacs 20.4 and the new 21.whatever series (both in 21.1 and 21.2), both bold and italic fonts have stopped changing size when the font size is changed. I have searched the archives to see if this was discussed, but I only found a complain or two in the nt list but no explanation. The PROBLEMS file included in the distribution I have (the nt one) is out of date about the font menu (which now works) and makes no mention of size problems for italic or bold fonts. I have tested this mostly in the nt version (Fabrice Popineau's latest binary build, of a very slightly out of date 21.2, on nt4, both on SP3 and SP5). In this case, changing the size from the font Size submenu of the Options menu changes the "basic" (ie non-bold, non-italic) font but leaves bold and italic at 10pt, and the effect is the same if I try this from custom (whether I save it to the .emacs file or not). I have also looked at 21.1.3 (Acadia) on Unix (Solaris 2.6) using Exceed 6 as my X server on a pc, where I only tested changing the font size from the menu, and the behaviour seems to be that italics and bold are ALWAYS in 10 pt no matter what the size is when set from the Size submenu of the Options menu. In fact, I have it set to 18pt in my .emacs file (otherwise the letters are too small to read properly through Exceed), and the bold and italics come as 10pt as well on startup before I change anything. (I could not find a PROBLEMS file in this distribution, taken from the binary distros in xemacs.org, I think built by Charles Wilson). This does not happen in 20.4 (we have that still installed on another machine), where the bold and italic fonts rescale happily with the default when changed from the menu, and they come up happily in 18pt when I bring XEmacs up (it's using exactly the same .emacs file as the 21.1.3 version, since my home directory is mounted across), and the size changes uniformly down to 8pt with no problems. My .emacs file is a very slight variation on the sample.emacs file. So this seems to be generally broken, and the breakage to have happened between 20.4 and 21.something (and still be there in 21.2) unless, of course, the problem lies in the use of a pc running nt as the display, though I think Exceed has its own font set, so it would be a big coincidence if both the Exceed and the native NT versions had the same problem. Is nobody else seeing this? Any ideas on what I might be doing wrong, if anything? Or is this a true bug (I don't believe this is the intended behaviour)? Thanks, all the best, Claudia PS I asked Andy Piper and he suggested I forward this to the mailing list to see if anyone has any insight on the problem -------------------------------------------------------------------------------------- For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group unless otherwise specifically stated. --------------------------------------------------------------------------------------

2 participants
1 comments

[crash] (while-t(all-hail-xemacs)) 25 years, 1 month

Robin S. Socha

Recompiled - still the same crash. In XEmacs 21.2 (beta23) "Hebe" [Lucid] (i686-pc-linux) of Tue Dec 14 1999 on radioactive.socha.net configured using `configure --compiler=egcs '-cflags=-g -I/usr/include/db1 -O6 -mcpu=pentiumpro -march=pentiumpro' --verbose --with-scrollbars=athena3d --with-dialogs=athena3d' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: Eval'ing (while-t(all-hail-xemacs)) with RedHat Linux 6.1. Lisp backtrace follows: play-sound-file("/usr/local/lib/xemacs/xemacs-packages/etc/sounds/im_so_happy.au") # bind (sound-file extensions data-dir) byte-code("..." [arg 0 face-list max-faces count "*Praise*" glyphp xemacs-logo p "\n" startup-center-spaces set-extent-begin-glyph make-extent "\n\n" insert-face xemacs-praise-message get-face random load-library "sound" xemacs-praise-sound-file split-string sound-extension-list ":" locate-data-directory "sounds" data-dir extensions sound-file file-exists-p device-sound-enabled-p sit-for play-sound-file wait-for-sounds 10] 7) # (unwind-protect ...) # bind (arg) praise-be-unto-xemacs(nil) # bind (arg) all-hail-xemacs() (while t (all-hail-xemacs)) ) eval((while t (all-hail-xemacs))) # bind (expr) eval-interactive((while t (all-hail-xemacs))) # bind (standard-output opoint ignore-quotes eval-last-sexp-arg-internal) eval-last-sexp(nil) # bind (command-debug-status) call-interactively(eval-last-sexp) # (condition-case ... . error) # (catch top-level ...) Aborted (core dumped) [robin＠radioactive robin]$ gdb /usr/src/XEmacs/CVS-21.2/xemacs/src/xemacs core 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-redhat-linux"... Core was generated by `/usr/src/XEmacs/CVS-21.2/xemacs/src/xemacs'. Program terminated with signal 6, Aborted. Reading symbols from /usr/lib/libesd.so.0...done. Reading symbols from /usr/lib/libaudiofile.so.0...done. Reading symbols from /lib/libm.so.6...done. Reading symbols from /usr/X11R6/lib/libXaw3d.so.6...done. Reading symbols from /usr/lib/libtiff.so.3...done. Reading symbols from /usr/lib/libpng.so.2...done. Reading symbols from /usr/lib/libjpeg.so.62...done. Reading symbols from /usr/lib/libz.so.1...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 /lib/libdl.so.2...done. Reading symbols from /lib/libdb.so.3...done. Reading symbols from /usr/lib/libgdbm.so.2...done. Reading symbols from /usr/lib/libgpm.so.1...done. Reading symbols from /usr/lib/libncurses.so.4...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. Reading symbols from /lib/libnss_files.so.2...done. #0 0x402ff4e1 in __kill () from /lib/libc.so.6 #0 0x402ff4e1 in __kill () from /lib/libc.so.6 #1 0x8083e11 in fatal_error_signal (sig=6) at emacs.c:276 #2 0x402ff408 in __restore () at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127 #3 0x40300868 in abort () at ../sysdeps/generic/abort.c:88 #4 0x8083d72 in assert_failed (file=0x81e9a3f "signal.c", line=340, expr=0x81e9a20 "async_timer_suppress_count > 0") at emacs.c:2825 #5 0x8152957 in alarm (howlong=0) at signal.c:340 #6 0x4001d788 in esd_open_sound () from /usr/lib/libesd.so.0 #7 0x4001d98e in esd_play_stream () from /usr/lib/libesd.so.0 #8 0x4001edf8 in esd_play_file () from /usr/lib/libesd.so.0 #9 0x80a6673 in esd_play_sound_file ( file=0xbfffea84 "/usr/local/lib/xemacs/xemacs-packages/etc/sounds/im_so_happy.au", vol=10) at esd.c:43 #10 0x8152eb8 in Fplay_sound_file (file=143656804, volume=136619780, device=136619780) at sound.c:142 #11 0x80890ad in Ffuncall (nargs=2, args=0xbfffeb60) at eval.c:3178 #12 0x80601f4 in execute_optimized_program ( program=0xbfffebbc "\b¬\004Áª\002\bÂ G\e\034Å\220Åq\210Æ\016\a!«\032`\036\bÉc\210Ê\016\a!j\210ËÌ``\"\016\a\"\210Íc\210)\fÁV\024Î\016\017ÐÑ\013!Â 8!\"\210\fS\211\024ªê\221\210*ÒÓ!«b\016\024Õ\016\026×\"ØÙ!\036\032\036\e\036\034Ý\016\034!¬\035Ý\016\032\016\034P!¬\024\016\e«\020\016\024\016\e＠P\026\034\016\eA\026\eªßÝ\016\034!«\005\016\034®\017Ý\016\032\016\034P!\006\016\032\016\034P\026\034Þ «\021\016\034«\rßÁ!\210à\016\034!\210á \210+ßâ!\207", stack_depth=7, constants_data=0x88d90b0) at bytecode.c:743 #13 0x8062e3a in Fbyte_code (instructions=143691444, constants=143495328, stack_depth=15) at bytecode.c:2400 #14 0x80885fd in Feval (form=143024920) at eval.c:2975 #15 0x808daab in Fprogn (args=143198580) at eval.c:767 #16 0x8060cb9 in execute_rare_opcode (stack_ptr=0xbfffee98, program_ptr=0x88d91ca "\207", opcode=Bsave_window_excursion) at bytecode.c:1236 #17 0x805ffc8 in execute_optimized_program (program=0x88d91c8 "À\213\207", stack_depth=1, constants_data=0x88e1380) at bytecode.c:653 #18 0x805fdee in funcall_compiled_function (fun=143704828, nargs=1, args=0xbfffef90) at bytecode.c:519 #19 0x8089223 in Ffuncall (nargs=2, args=0xbfffef8c) at eval.c:3210 #20 0x80601f4 in execute_optimized_program (program=0x88d91b0 "À\t!\207\031", stack_depth=2, constants_data=0x88d9170) at bytecode.c:743 #21 0x805fdee in funcall_compiled_function (fun=143704884, nargs=0, args=0xbffff018) at bytecode.c:519 #22 0x8088940 in Feval (form=143023612) at eval.c:3034 #23 0x808559d in Fwhile (args=143023600) at eval.c:767 #24 0x8088452 in Feval (form=143023588) at eval.c:2947 #25 0x8089085 in Ffuncall (nargs=2, args=0xbffff290) at eval.c:3178 #26 0x80601f4 in execute_optimized_program ( program=0x87b7700 "\b¢Áa«!\bGÂV«\eÃÄ\bAB!\210\r«\rÆÇ!\210ÈÉ!\210ÆÊ!\210\bA＠\207\b¢Ëa«0\bGÂV«*Ì\bA＠!«#Í\bA＠ÃÂ\b8!\"\210Ã\b!\210\r«\rÆÎ!\210ÈÉ!\210ÆÊ!\210\bA＠\207Ã\b!\207", stack_depth=5, constants_data=0x83cdf20) at bytecode.c:743 #27 0x805fdee in funcall_compiled_function (fun=138168760, nargs=1, args=0xbffff39c) at bytecode.c:519 #28 0x8089223 in Ffuncall (nargs=2, args=0xbffff398) at eval.c:3210 #29 0x80601f4 in execute_optimized_program ( program=0x87b58c8 "\b«\004pª\002Á`Â\e\034\035ÆÇÈ \036\tÊ\216Ë\016\f!\210\212ÂfÍa®\005Î Ía\023ÏÐ!\210\013«\nÂfÑa«\004Âu\210\214e\f}\210Òp!\211\036\023¢Ôa«\rÕÖ×\016\023ØBBBDª\003\016\023-!!+\207", stack_depth=8, constants_data=0x83cdf70) at bytecode.c:743 #30 0x805fdee in funcall_compiled_function (fun=138168788, nargs=1, args=0xbffff4ac) at bytecode.c:519 #31 0x8089223 in Ffuncall (nargs=2, args=0xbffff4a8) at eval.c:3210 #32 0x8065382 in Fcall_interactively (function=137707588, record_flag=136619780, keys=136619780) at callint.c:946 #33 0x80878bd in Fcommand_execute (cmd=137707588, record=136619780, keys=136619780) at eval.c:2613 #34 0x80b9a22 in execute_command_event (command_builder=0x82bebe8, event=143608248) at event-stream.c:4333 #35 0x80ba5a1 in Fdispatch_event (event=143608248) at event-stream.c:4644 #36 0x806a27b in Fcommand_loop_1 () at cmdloop.c:575 #37 0x806a4bd in command_loop_1 (dummy=136619780) at cmdloop.c:490 #38 0x808d7bb in condition_case_1 (handlers=136619876, bfun=0x806a478 <command_loop_1>, barg=136619780, hfun=0x8069690 <cmd_error>, harg=136619780) at eval.c:1630 #39 0x806a59c in command_loop_2 (dummy=136619780) at cmdloop.c:252 #40 0x808d68f in internal_catch (tag=136693732, func=0x806a564 <command_loop_2>, arg=136619780, threw=0x0) at eval.c:1305 #41 0x8069aad in initial_command_loop (load_me=136619780) at cmdloop.c:301 #42 0x8082404 in sort_args (argc=1, argv=0xbffff9c4) at emacs.c:1898 #43 0x808401e in main (argc=1, argv=0xbffff9c4, envp=0xbffff9cc) at emacs.c:2323 #44 0x402f91eb in __libc_start_main (main=0x8083f1c <main>, argc=1, argv=0xbffff9c4, init=0x804dcd8 <_init>, fini=0x81a6b80 <_fini>, rtld_fini=0x4000a610 <_dl_fini>, stack_end=0xbffff9bc) at ../sysdeps/generic/libc-start.c:90 Recent keystrokes: misc-user Recent messages (most recent first): Loading mail-abbrevs... Loading emacsbug...done Loading emacsbug...

1 participants
0 comments

crash in call-process-internal 25 years, 1 month

Cotton Seed

I was doing M-! (shell-command) of: mv Tiger_FragmentTemplateMatch_RuleSet.C Tiger_FragmentMatch_RuleSet.C and xemacs with a failed assertion. It did not execute the mv command before the crash. I'm on redhat6.0. I am not able to reproduce the crash. - Cotton Fatal error: assertion failed, file lisp.h, line 969, RECORD_TYPEP (obj, &lrecord_string) 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/xemacs-21.2.23/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: call-process-internal("/bin/bash" "/tmp/emacsNzCT3M" #<buffer "*Shell Command Output*"> nil "-c" "mv Tiger_FragmentTemplateMatch_RuleSet.C Tiger_FragmentMatch_RuleSet.C") apply(call-process-internal "/bin/bash" "/tmp/emacsNzCT3M" #<buffer "*Shell Command Output*"> nil ("-c" "mv Tiger_FragmentTemplateMatch_RuleSet.C Tiger_FragmentMatch_RuleSet.C")) # bind (args displayp buffer infile program) call-process("/bin/bash" "/tmp/emacsNzCT3M" #<buffer "*Shell Command Output*"> nil "-c" "mv Tiger_FragmentTemplateMatch_RuleSet.C Tiger_FragmentMatch_RuleSet.C") apply(call-process "/bin/bash" "/tmp/emacsNzCT3M" #<buffer "*Shell Command Output*"> nil ("-c" "mv Tiger_FragmentTemplateMatch_RuleSet.C Tiger_FragmentMatch_RuleSet.C")) # (unwind-protect ...) # bind (temp args displayp buffer deletep program end start) call-process-region(956 956 "/bin/bash" nil #<buffer "*Shell Command Output*"> nil "-c" "mv Tiger_FragmentTemplateMatch_RuleSet.C Tiger_FragmentMatch_RuleSet.C") # (unwind-protect ...) # bind (buffer success exit-status directory replace output-buffer command end start) shell-command-on-region(956 956 "mv Tiger_FragmentTemplateMatch_RuleSet.C Tiger_FragmentMatch_RuleSet.C" nil) # (unwind-protect ...) # bind (match-data output-buffer command) #<compiled-function (command &optional output-buffer) "...(66)" [output-buffer bufferp barf-if-buffer-read-only push-mark call-process shell-file-name nil t shell-command-switch command exchange-point-and-mark match-data match-data (...) string-match "[ ]*&[ ]*$" background 0 shell-command-on-region] 7 699164 (list (read-shell-command "Shell command: ") current-prefix-arg)>("mv Tiger_FragmentTemplateMatch_RuleSet.C Tiger_FragmentMatch_RuleSet.C" nil) call-interactively(shell-command) # (condition-case ... . error) # (catch top-level ...)

1 participants
0 comments

Re: Bold and Italic fonts 25 years, 1 month

Jody M. Klymak

>>>>> "cy" == claudia yastremiz <claudia.yastremiz(a)barclayscapital.com> writes: cy> Is nobody else seeing this? Any ideas on what I might be doing cy> wrong, if anything? Or is this a true bug (I don't believe cy> this is the intended behaviour)? Hi Claudia, I get the same thing with all the builds of 21.* that I've managed to get working on my NT machine. Some people claim to not have the problem, though I wonder if thats really true or if they simply leave the fonts at 10 pts.... BTW, you need to test it with real bold and real italic fonts to see the problem. The three start-up buffers that cycle before you open any files is a good set of test buffers. Cheers, Jody -- Jody Klymak APL/School of Oceanography, Doctoral Candidate University of Washington mailto:jklymak＠apl.washington.edu (206)-685-9080 http://www.ocean.washington.edu/people/grads/jklymak/

1 participants
0 comments

2025

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 1999