December 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: XEmacs 21.2.23 crashes when url-insert-file-contents 26 years

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > > > jan wrote > > > > > Are you sure about that? > > Sorry, I was unclear (wrong citing). I meant "are you sure about it > crashing in report_extent_modification_mapper?". The backtrace seems to indicate that it crashes in map_extents, which is called by report_extent_modification_mapper() to see if any extents have modification functions hooked into them.

1 participants
0 comments

Re: More ESD ./configure bogosity 26 years

Raymond Toy

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: >>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Raymond Toy <toy(a)rtp.ericsson.se> writes: >>> >> Why can't we reliably detect NAS? Isn't the existence of a few >>> >> include files and libaudio enough? Jan> I now remember another reason why this is probably not autodetected at Jan> the moment (but which is no longer valid). It used to be that NAS Jan> always was a thing you had to install yourself and thus was never in Jan> any obvious location. However on modern Free Unix'es that is no longer Jan> the case. >>> Why would you have to do that? Wouldn't configure just try to compile >>> something like Jan> You are right... Martin> I put in some brief work to get NAS working, but... Martin> - it's no longer maintained. There's nas 1.3 out now. Someone did pick up nas, but the mailing list has been relatively quiet. Martin> - it seems like there's a new wave of Sound support coming with ESD. Any web pointers to ESD? I hope they're not just reinventing the wheel. Martin> So I'm not going to do any more work on NAS configure support. Martin> Someone who cares can do it. Is there anyone else using NAS besides me? If not, I guess NAS and xemacs is basically dead. Too bad. Ray

3 participants
4 comments

Re: XEmacs 21.2.23 crashes when url-insert-file-contents 26 years

Gunnar Evermann

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: [snip David's recipe incl. widen/narrowing ] > > this instantly triggers the assertion. > > Note that it triggers this even in a non-mule emacs...! yes and that's what I looked at more closely. The problem is quite simple actually. (I'm not quite sure whether Shenghuo's crash is the same problem -- Bill what kind of stuff are you doing in that after-change-functions?). A new and improved test case is: ----- (switch-to-buffer "FOO") (insert "123456") (defun acf (start end len) (goto-char 4) (delete-char 2)) (setq after-change-functions '(acf)) (insert "a") ----- No narrowing necessary. What happens is that when inserting the "a" we call: signal_after_change(buf = 0x824000, start = 7, orig_end = 7, new_end = 8) this runs acf, which in turn deletes two characters, making bufz=6. 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. I am surprised we don't see this more often. What do people usually use this after-change stuff for? any suggestions for a fix? Gunnar

2 participants
1 comments

XEmacs is too self-conscious... 26 years

Robin S. Socha

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 (beta23) "Hebe" [Lucid] (i686-pc-linux) of Tue Dec 7 1999 on radioactive.socha.net configured using `configure --compiler=egcs '-cflags=-I/usr/include/db1 -O6 -mcpu=pentiumpro -march=pentiumpro' --error-checking=none --debug=no --verbose --with-scrollbars=athena3d --with-dialogs=athena3d' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I tried eval'ing (while t(all-hail-xemacs) 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) #0 0x402ff4e1 in __kill () from /lib/libc.so.6 #1 0x8078c21 in fatal_error_signal () #2 0x402ff408 in __restore () at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127 #3 0x40300868 in abort () at ../sysdeps/generic/abort.c:88 #4 0x8078b82 in assert_failed () #5 0x8113b67 in alarm () #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 0x8092223 in esd_play_sound_file () #10 0x811407f in Fplay_sound_file () #11 0x807c3ad in Ffuncall () #12 0x805b25f in execute_optimized_program () #13 0x805d2c3 in Fbyte_code () #14 0x807babd in Feval () #15 0x80801ab in Fprogn () #16 0x805bbb9 in execute_rare_opcode () #17 0x805b092 in execute_optimized_program () #18 0x805af26 in funcall_compiled_function () #19 0x807c522 in Ffuncall () #20 0x805b25f in execute_optimized_program () #21 0x805af26 in funcall_compiled_function () #22 0x807bd1e in Feval () #23 0x80807f4 in Fwhile () #24 0x807b999 in Feval () #25 0x807c385 in Ffuncall () #26 0x805b25f in execute_optimized_program () #27 0x805af26 in funcall_compiled_function () #28 0x807c522 in Ffuncall () #29 0x805b25f in execute_optimized_program () #30 0x805af26 in funcall_compiled_function () #31 0x807c522 in Ffuncall () #32 0x805f1e2 in Fcall_interactively () #33 0x807b20d in Fcommand_execute () #34 0x809f418 in execute_command_event () #35 0x809fc46 in Fdispatch_event () #36 0x8062cab in Fcommand_loop_1 () #37 0x8062ebe in command_loop_1 () #38 0x807ff63 in condition_case_1 () #39 0x8062f9c in command_loop_2 () #40 0x807fe3f in internal_catch () #41 0x80629dc in initial_command_loop () #42 0x807759f in xemacs_21_2_b23_i686_pc_linux () #43 0x8078e1e in main () #44 0x402f91eb in __libc_start_main (main=0x8078d1c <main>, argc=1, argv=0xbffffa14, init=0x804dc18 <_init>, fini=0x8157720 <_fini>, rtld_fini=0x4000a610 <_dl_fini>, stack_end=0xbffffa0c) at ../sysdeps/generic/libc-start.c:90

1 participants
0 comments

Re: XEmacs 21.2.23 crashes when url-insert-file-contents 26 years

Jan Vroonhof

Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: > No narrowing necessary. What happens is that when inserting the "a" > we call: > > signal_after_change(buf = 0x824000, start = 7, orig_end = 7, new_end = 8) > > this runs acf, which in turn deletes two characters, making bufz=6. > > 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. Aha...! Good spotting. From the type of assert Shengo gets that might very well be the same bug (at the very least the assert has to do with running unexpectically against the buffer boundary). > I am surprised we don't see this more often. What do people usually > use this after-change stuff for? To set up extents (i.e. font-locking)...Changing the buffer like this is evil (allthough the new flyspell autocorrect stuff does also does things like that, it just sets of a hook of things to do later on the post-command hook/idle timer). Note that one doesn't notice this with normal after-change-functions because it is very rare to have many of them and because the positions are converted to lisp ints first and thus are subject to validation when they are used. > any suggestions for a fix? The trivial change would be simply check the validity of the two positions before using them to map over extents. This then simply means "real changes to the buffer in after-change-functions loses" (A quick test[1] shows that this corresponds to what FSF 20.4 does) The fancy answer would be to use markers to preserve the positions along calls to lisps. However doing that without allocating lots of unneed trash markers might well be difficult Jan P.S. You might want to make your example into a test case. Footnotes: [1] Running (switch-to-buffer "FOO") (insert "123456") (defun reportargs (&rest args) (with-current-buffer (get-buffer-create "traceme") (insert (format "%s\n" args)))) (defun acf (start end len) (goto-char 4) (delete-char 2)) (setq after-change-functions '(reportargs acf reportargs)) (insert "a") shows that FSF 20.4 calls 'reportargs' with the same arguments (7 8 nil) both times. Running this on "xenacs-21.1.8 -vanilla" makes XEmacs go mad!

1 participants
0 comments

Re: Xt exits still occurring 26 years

Jan Vroonhof

Karl Kleinpaste <karl(a)justresearch.com> writes: > Spoke too soon. The usual nightmare: > Error: Widget *Article* has zero width and/or height > > The usual stack trace, and the usual xwininfo -tree dump. :-( Jan

1 participants
0 comments

Re: Xt exits still occurring 26 years

Karl Kleinpaste

/mutter/ Spoke too soon. The usual nightmare: Error: Widget *Article* has zero width and/or height The usual stack trace, and the usual xwininfo -tree dump.

1 participants
0 comments

Re: vhdl-mode 3.30 26 years

Jan Vroonhof

[Eric Ludlam and XEmacs beta CC'ed] Andreas Jaeger <aj(a)suse.de> writes: > >>>>> Jan Vroonhof writes: > > > Reto Zimmermann <reto(a)synopsys.com> writes: > >> Are you sure your speedbar version includes the changes of 1999/11/29 > >> which fixed a major bug for Windows XEmacs (recognition of backslashes > >> in directory paths)? > > > Given that our version dates from September, probably not. > > However which changes are you talking about, our version is based on > > speedbar-0.8.1 which is still the latest version on > > http://www.ultranet.com/~zappo/speedbar.html > > There's a newer version (0.9bovine1) directly at > http://choochoo.ultranet.com/~zappo/fsf.shtml. I can send the version > if you need it. I don't like taking development versions without the authors involvement, especially not as Eric indicated he was in the midst of a major rewrite. I have CC'ed Eric now. Eric, what would you prefer? >From what I see his latest version still has a lot the potential problems. It would be nice if somebody could help Eric and rewrite all these and send him a patch (which we could apply to 0.8.1 as a stop-gap). Typical example (setq rt (concat (expand-file-name rt) (if (string-match "[/\\]\\'" rt) "" "/") (file-name-nondirectory f)))) This may match both separators now, but it is much more cleanly written as (setq rt (expand-file-name (file-name-non-directory f) rt)) Jan

2 participants
1 comments

Re: First Packages *TEST* release 26 years

Jan Vroonhof

Andreas Jaeger <aj(a)suse.de> writes: > > *) the new ispell package does not work with aspell, an ispell replacement. > > <http://metalab.unc.edu/kevina/aspell/>. I have not investigated > > much, it appears to start up then bomb out with an error 255. I'm > > guessing some type of command line switch changed, but am not sure at > > this point. > Could you check this, please? Yes, please do > > which package changed to make pgnus use the progress bar thingie? > No idea. I haven't seen that myself. The new w3 is the only one using the progress bar's. It is not the packages fault. Jan

2 participants
1 comments

Adding Homepage of different packages 26 years

Andreas Jaeger

The Makefile of the various xemacs-packages contain some information on the packages. I do miss a place where the home page is recorded. I'd like to add this to the Makefiles and also get this into the package index. Besides having a single place where this is documented, I'd like to automatically generate a web page from package-index that contains some information about the latest packages. Any objections or better ideas? Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.rhein-neckar.de

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