August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

21.2.19 assert failure, editing in minibuf 25 years, 3 months

Karl Kleinpaste

I was editing a minibuf prompt, which had a default response that I was altering. I had backed up to the first character in the minibuf, a comma, and hit M-BS a last time (after deleting several words beforehand) to eliminate it. (Specifically, a Keywords: specification in a reply in Gnus.) Program received signal SIGABRT, Aborted. 0x2ad2a811 in __kill () (gdb) bt #0 0x2ad2a811 in __kill () #1 0x2ad2a63f in raise (sig=6) at ../sysdeps/posix/raise.c:27 #2 0x2ad2b84f in abort () at ../sysdeps/generic/abort.c:83 #3 0x808e0ef in assert_failed (file=0x8221d38 "insdel.c", line=607, expr=0x8221dbb "( newmin) > BI_BUF_BEG (buf) && newmin <= BI_BUF_Z (buf)") at emacs.c:2672 #4 0x81360f3 in bufpos_to_bytind_func (buf=0x8318ee8, x=0) at insdel.c:607 #5 0x8136aa7 in bufpos_to_bytind (buf=0x8318ee8, x=0) at buffer.h:986 #6 0x81a1b08 in scan_words (buf=0x8318ee8, from=1, count=-1) at syntax.c:427 #7 0x81a1e3e in Fforward_word (count=-1, buffer=137162676) at syntax.c:476 #8 0x8064135 in execute_rare_opcode (stack_ptr=0x7fffe8a0, program_ptr=0x8984eb1 "\210`)\"\207Ú*à\004", opcode=Bforward_word) at bytecode.c:1390 #9 0x80631a8 in execute_optimized_program ( program=0x8984eac "À`\212\tv\210`)\"\207Ú*à\004", stack_depth=3, constants_data=0x83e3740) at bytecode.c:657 #10 0x8062d15 in funcall_compiled_function (fun=138266820, nargs=1, args=0x7fffe9a0) at bytecode.c:523 #11 0x8094dcd in Ffuncall (nargs=2, args=0x7fffe99c) at eval.c:3221 #12 0x8063404 in execute_optimized_program ( program=0x8b1a9c4 "À\t[!\207N\230\b", stack_depth=2, constants_data=0x83e3f60) at bytecode.c:747 #13 0x8062d15 in funcall_compiled_function (fun=138266848, nargs=1, args=0x7fffeaa4) at bytecode.c:523 #14 0x8094dcd in Ffuncall (nargs=2, args=0x7fffeaa0) at eval.c:3221 #15 0x8069a1a in Fcall_interactively (function=138233844, record_flag=137162676, keys=137162676) at callint.c:949 #16 0x8093457 in Fcommand_execute (cmd=138233844, record=137162676, keys=137162676) at eval.c:2623 #17 0x80e1616 in execute_command_event (command_builder=0x8361868, event=145620480) at event-stream.c:4345 #18 0x80e2452 in Fdispatch_event (event=145620480) at event-stream.c:4684 #19 0x8073320 in Fcommand_loop_1 () at cmdloop.c:578 #20 0x807309d in command_loop_1 (dummy=137162676) at cmdloop.c:493 #21 0x8091785 in condition_case_1 (handlers=137162772, bfun=0x807304c <command_loop_1>, barg=137162676, hfun=0x80724d0 <cmd_error>, harg=137162676) at eval.c:1640 #22 0x8072994 in call_command_loop (catch_errors=137162700) at cmdloop.c:255 #23 0x81537bf in Fread_minibuffer_internal (prompt=150105212) at minibuf.c:188 #24 0x8094c60 in Ffuncall (nargs=2, args=0x7fffee10) at eval.c:3189 #25 0x8063404 in execute_optimized_program ( program=0x7fffee5c "À Á V«\013Â\211\e\034Å\016\006!*\207Å\016\006!\207Ô*ÌfÚ* $Ú*\230P$\b(]£\b\004Å$\b8$Ú*´ï,\b\"", stack_depth=2, constants_data=0x84022a8) at bytecode.c:747 #26 0x806748c in Fbyte_code (instructions=138373516, constants=138420888, stack_depth=5) at bytecode.c:2406 #27 0x809423a in Feval (form=138419868) at eval.c:2986 #28 0x8091360 in internal_catch (tag=137250916, func=0x8093980 <Feval>, ---Type <return> to continue, or q <return> to quit--- arg=138419868, threw=0x0) at eval.c:1315 #29 0x8063f34 in execute_rare_opcode (stack_ptr=0x7ffff08c, program_ptr=0x8c34c1c "æa«\f\201H", opcode=Bcatch) at bytecode.c:1253 #30 0x80631a8 in execute_optimized_program ( program=0x8c34aac "\b¬\022Á ÂV«\fÃ Ä a«\005ÅÆ!\210\016\a«\021\016\aÂV«\013Á \016\aY«\004È \210\016\t«\"\016\t9«\017Ê\016\t!¬\027ÅË\016\t\"\210ª\017Ê\016\t＠!¬\bÅË\016\t＠\"\210Ì «\tÍÎÏ\016\020!\"\210\016\021\036\022Ã \036\023Ô \036\025Ä \036\026Á Âa«\a×\016\026!ª\bØÙÚÁ \"!\036\eÜ\016\026!\211\036\035Ô a?\005Þ\016\035!\036\037Þ \036 \016\t\036!â\216ã\016\e!q\210\016\022\026\021äå!\210æ\026%äç!\210äè!\210äé!\210ê\026'ë\026(\016,«\025äí!\210\016-"..., stack_depth=6, constants_data=0x8402358) at bytecode.c:657 #31 0x8062d15 in funcall_compiled_function (fun=138421444, nargs=5, args=0x7ffff19c) at bytecode.c:523 #32 0x8094dcd in Ffuncall (nargs=6, args=0x7ffff198) at eval.c:3221 #33 0x8063404 in execute_optimized_program ( program=0x8a393dc "À\031Â\013\f\rÀ\016\006%)\207", stack_depth=6, constants_data=0x8403108) at bytecode.c:747 #34 0x8062d15 in funcall_compiled_function (fun=138422228, nargs=2, args=0x7ffff2ac) at bytecode.c:523 #35 0x8094dcd in Ffuncall (nargs=3, args=0x7ffff2a8) at eval.c:3221 #36 0x8063404 in execute_optimized_program ( program=0x8876e2c "\bÁa«\003Â\020\bÂa¬\013\bÃa¬\006\bÄa«\037\r«\030\r\036\006ÇÈ\016\006\"«\t\016\006É\225ÄOª\003\016\006)ª\002Ê\025ª\n\bËa«\005Ì\r!\025Í\016\016!ÏÐ\016\021\227\"Ä\036\022\036\021\036\016\016\023«/ÔÏÕ\016\026×a«\004Øª\n\016\026;«\004Ùª\002Ú\016\021\016\016ÉW«\004Ûª\002Ü$\r§«\006Ý\r!ª\002\r\"\025ÏÐ\r\"\025Þß\016\021\016 \"8áa«\005â\r!\025\016\026×a\204æ", stack_depth=7, constants_data=0x8a1bd18) at bytecode.c:747 #37 0x8062d15 in funcall_compiled_function (fun=144704532, nargs=8, args=0x7ffff3c0) at bytecode.c:523 #38 0x8094dcd in Ffuncall (nargs=9, args=0x7ffff3bc) at eval.c:3221 #39 0x8063404 in execute_optimized_program ( program=0x8c17db4 "À\t!\211\032ÃW«\004Äª\002Å\036\006\nÃV\036\aÈ\036\tÊ\036\013\016\f\036\rÎÏ ÐEÑÒE\036\023\016\024\036\025\016\026\a×\016\026!ÃH\036\030\016\031\a×\016\031!ÃH\036\032\016\e\a×\016\e!ÃH\036\034Ý\036\036Ý\036\037Ý\036 Ý\036!Ý\036\"ã\216\016\030¬>\016\025«\räå!\210æç\016\006\"\210ª\023æè\016\a«\004éª\002êëì\016\tí##\210î \211\026\030ïU¬\a\016\030ðU«ÌÝ\026\030ñò\016\tå#\210ªÀó \210\016\030\227\016\t·\211\026\036¬\023\016\025«\013ôõ\016\006\016\030#\210ª\005ôö!\210\016\030\227\016\030U"..., stack_depth=10, constants_data=0x8a199a8) at bytecode.c:747 #40 0x8062d15 in funcall_compiled_function (fun=144704392, nargs=2, args=0x7ffff4dc) at bytecode.c:523 #41 0x8094dcd in Ffuncall (nargs=3, args=0x7ffff4d8) at eval.c:3221 #42 0x80954ae in Fapply (nargs=2, args=0x7ffff520) at eval.c:3456 #43 0x8095cd2 in apply1 (fn=144704392, arg=150660704) at eval.c:3808 #44 0x8067ee4 in Fcall_interactively (function=141580252, record_flag=137162676, keys=137162676) at callint.c:397 #45 0x8093457 in Fcommand_execute (cmd=141580252, record=137162676, keys=137162676) at eval.c:2623 ---Type <return> to continue, or q <return> to quit--- #46 0x80e1616 in execute_command_event (command_builder=0x8361868, event=143865704) at event-stream.c:4345 #47 0x80e2452 in Fdispatch_event (event=143865704) at event-stream.c:4684 #48 0x8073320 in Fcommand_loop_1 () at cmdloop.c:578 #49 0x807309d in command_loop_1 (dummy=137162676) at cmdloop.c:493 #50 0x8091785 in condition_case_1 (handlers=137162772, bfun=0x807304c <command_loop_1>, barg=137162676, hfun=0x80724d0 <cmd_error>, harg=137162676) at eval.c:1640 #51 0x8073538 in command_loop_2 (dummy=137162676) at cmdloop.c:255 #52 0x8091360 in internal_catch (tag=137236964, func=0x8073504 <command_loop_2>, arg=137162676, threw=0x0) at eval.c:1315 #53 0x8072937 in initial_command_loop (load_me=137162676) at cmdloop.c:304 #54 0x808cfa1 in xemacs_21_2_b19_i686_pc_linux (argc=5, argv=0x7ffff994, envp=0x7ffff9ac, restart=0) at emacs.c:1763 #55 0x808d72d in main (argc=5, argv=0x7ffff994, envp=0x7ffff9ac) at emacs.c:2188 (gdb) uname -a: Linux beaver.jprc.com 2.2.10-ac10 #1 SMP Tue Jul 13 13:23:27 EDT 1999 i686 unknown ./configure '--with-pop' '--with-mule' '--with-png' XEmacs 21.2-b19 "Shinjuku" configured for `i686-pc-linux'. Where should the build process find the source code? /home/karl/src/x/xemacs-21/xemacs-21.2.19 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DSO module support. movemail will use "dot-locking" for locking mail spool files. Using POP for mail access. Compiling in extra code for debugging. 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: ---------------------------------------------------------

1 participants
0 comments

Re: bug w/file-coding & processes 25 years, 3 months

Jan Vroonhof

Darryl Okahata <darrylo(a)sr.hp.com> writes: > Unfortunately, `nil' represents the "binary" coding system. If > `coding-system-for-read' is `undecided' when subprocess input is > read, the first few (512?) bytes are examined to determine the This is what the Lispref says Coding System Types ------------------- `nil' `autodetect' Automatic conversion. XEmacs attempts to detect the coding system used in the file. So it at least used to be correct (the lispref doesn't know about 'undecided). Given that is almost the only documentation there is about this stuff would it be possible to update the documentation first? Jan BTW nil == undecided is used is used in many more places and probably even it 3rd party code.

2 participants
1 comments

bug w/file-coding & processes 25 years, 3 months

Darryl Okahata

Scenario: XEmacs 21.1.4 w/file-coding but not MULE (I think MULE is irrelevant, for this bug) Problem: When reading binary subprocess input (from crypt, pgp, etc.), `call-process' in code-process.el sets `coding-system-for-read' to `undecided', if `coding-system-for-read' is nil. Unfortunately, `nil' represents the "binary" coding system. If `coding-system-for-read' is `undecided' when subprocess input is read, the first few (512?) bytes are examined to determine the EOL type. Unfortunately, when reading binary input, \r (CR) is a valid character, and will make the file-coding lstream input think that CR to LF translation is required, which will corrupt the input. This is, er, "interesting"; `coding-system-for-read' needs to be `nil' (for binary input), but `call-process' insists on setting it to be `undecided'. I'm not sure what to do. Perhaps we should allow both `t' and `nil' to represent binary? In other words, these would be equivalent: (get-coding-system nil) ;; for backwards compatibility (get-coding-system t) Perhaps we should add an explicit binary coding name? Comments? In the meantime, I've kludged around the problem by not having `call-process' set `coding-system-for-read' to be `undecided'. I suspect this bug also exists in 21.2. -- Darryl Okahata darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.

2 participants
1 comments

Re: Recent XEmacs package building changes 25 years, 3 months

Didier Verna

Steve Baur wrote: > > This causes problems for me since there are packages I don't want > > to install and I don't want to compile at all (they are checked > > out, however, since it's simpler to call `cvs co' only once, at the > > toplevel directory). > > Do a `make distclean; cd ..; cvs release -d <unwanted-package>' to get > rid of the source of unwanted packages. `cvs update' does not [re]create > directories, so you should be able to continue updating when necessary. Yes, but this means that I'll have to checkout manually any new package that appears in the tree, right ? Usually, I just `cvs update -Pd' at the toplevel. If I keep on doing this, the effect of the `cvs release' command will be lost. > > Actually, since I never could checkout skk properly, the make process > > bombs out on this one and I have to modify the SUBDIRS variable of > > its Makefile by hand to remove it from the make process. > > ? Can you provide any more details? This is a problem I add for ages. Each time I check out skk, the command fails saying something like "could not allocate 32 bytes". I talked with Jareth about this, and he advised me NOT to use cvs 1.10.2. But I never took the time to compile another version than the one we have installed here. > Can you delete the source as > described above, then do `cvs update -d skk' > to get good source? cvs [server aborted]: out of memory; can not allocate 41 bytes cvs release: unable to release `skk' > Something else is required for doing a partial bytecompile. Would you > consider a marker file sufficient? For example, if you could touch a > `.nobuild' file in the packages you never want to build, would that > work for you? Sure. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Re: Ack! 25 years, 3 months

Didier Verna

wmperry(a)aventail.com (William M. Perry) wrote: > Don't try to visit any other files after visiting one in C++ mode in the > latest CVS tree. I've just submitted a patch for this. > It's fatal: Yes, it (*＠#%$!#^$) is :-) -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

Ack! 25 years, 3 months

William M. Perry

Don't try to visit any other files after visiting one in C++ mode in the latest CVS tree. It's fatal: Signaling: (invalid-regexp "Invalid preceding regular expression") string-match("c++-" "efs-mode") select-buffers-tab-buffers-by-mode(#<buffer "config_data.cpp"> #<buffer "*ftp anonymous(a)ftp.xemacs.org*">) #<compiled-function (buf) "...(5)" [buffers-tab-selection-function first-buf buf] 3>(#<buffer "*ftp anonymous(a)ftp.xemacs.org*">) delete*(nil (#<buffer "config_data.cpp"> #<buffer "*ftp anonymous(a)ftp.xemacs.org*">) :if-not #<compiled-function (buf) "...(5)" [buffers-tab-selection-function first-buf buf] 3>) apply(delete* nil (#<buffer "config_data.cpp"> #<buffer "*ftp anonymous(a)ftp.xemacs.org*">) :if-not #<compiled-function (buf) "...(5)" [buffers-tab-selection-function first-buf buf] 3> nil) delete-if-not(#<compiled-function (buf) "...(5)" [buffers-tab-selection-function first-buf buf] 3> (#<buffer "config_data.cpp"> #<buffer "*ftp anonymous(a)ftp.xemacs.org*">)) buffers-tab-items(t) remove-buffer-from-gutter-tab() kill-buffer("*Backtrace*") call-interactively(kill-buffer) Evidently someone needs to be doing a regexp-quote.... -bp

1 participants
0 comments

window-edges in Calc package 1.10 25 years, 3 months

Mikio Nakajima

While Calc still uses `window-edges, XEmacs does not have it. So, calc-delete-windows-keep in calc-misc.el (which uses the function) should be replaced by following for examples; (defun calc-delete-windows-keep (&rest bufs) (dolist (buf bufs) (delete-windows-on buf) ))) Thank you. Mikio Nakajima <minakaji(a)osaka.email.ne.jp> <minakaji(a)pdx.ne.jp> http://www.asahi-net.or.jp/~gy2m-nkjm/

1 participants
0 comments

patch for latest gutter fixes 25 years, 3 months

Damon Lipparelli

I had to make the attached change to get things compiling under WinNT (using VC++ 5sp3). 1999-08-08 Damon Lipparelli <lipp(a)primus.com> * window.c (Fcurrent_pixel_column): add empty statement to shut up the windows compiler. -lipp 1999-08-08 Damon Lipparelli <lipp(a)primus.com> * window.c (Fcurrent_pixel_column): add empty statement to shut up the windows compiler. Index: window.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/window.c,v retrieving revision 1.41.2.12 diff -u -r1.41.2.12 window.c --- window.c 1999/08/08 13:50:13 1.41.2.12 +++ window.c 1999/08/08 19:15:09 ＠＠ -5521,6 +5521,7 ＠＠ } return Qnil; found_bufpos: + ; } else {

2 participants
1 comments

More gutter fixes. 25 years, 3 months

Andy Piper

This patch fixes some more gutter problems including some nasty redisplay bugs. I also have included motif combo-box support and the window-pixel-column stuff. I have fixed the buffer tab to now group buffers based upon the major mode of the current buffer. You can switch it off by setting buffers-tab-selection-function to nil. Let me know what you think. I will apply this andy or glyphs_changed as if it is the subwindow cache will have been reset. 1999-08-06 Andy Piper <andyp(a)beasys.com> * gui-x.c (button_item_to_widget_value): cope with strings. * glyphs.h: declare global widget functions. (IIFORMAT_HAS_SHARED_DEVMETHOD): new macro. * glyphs-x.c (x_combo_box_instantiate): do generic initialization here. remove dead code. (image_instantiator_format_create_glyphs_x): enable combo boxes for Motif 2.0. * glyphs-widget.c (widget_instantiate_1): make non-static. (tree_view_instantiate): renamed from combo_box_instantiate. (image_instantiator_format_create_glyphs_widget): use new/changed methods. * glyphs-msw.c (mswindows_combo_box_instantiate): do generic initialization here. * lwlib-Xm.c (xm_update_combo_box): new function. (xm_update_one_widget): call it. (xm_update_one_value): deal with combo boxes as well as lists. (xm_create_combo_box): create a drop-down combo box. * gutter-items.el (buffers-tab-max-size): set custom selection default to 6. (buffers-tab-switch-to-buffer): just switch window if the window is visible. (add-tab-to-gutter): set face as default. * toolbar-msw.c (mswindows_output_toolbar): call mswindows_move_toolbar. 1999-08-05 Andy Piper <andyp(a)beasys.com> * window.c (Fcurrent_pixel_column): new function. use display lines to calculate pixel position of point. * window.c (syms_of_window): declare it. -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

Misleading information on ~/.xemacs/packages 25 years, 3 months

Nick V. Pakoulin

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 (beta19) "Shinjuku" [Lucid] (i686-pc-linux) of Sat Aug 7 1999 on pegas.kazbek.ispras.ru configured using `configure --debug=no --error-checking=none --with-pop' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: On August 7 1999 I have upgraded my XEmacs 21.2 (beta13) to XEmacs 21.2 (beta19) and found that my own packages, placed in ~/.xemacs are no longer available. BUT in xemacs-21.2.19/INSTALL I found, that ... By default, packages will be searched for in the path ~/.xemacs::$prefix/lib/xemacs-${version}/mule-packages:$prefix/lib/xemacs/mule-packages:$prefix/lib/xemacs-${version}/xemacs-packages:$prefix/lib/xemacs/xemacs-packages ... Then I looked through the NEWS (C-h n) and found the following : ... ** XEmacs now locates the early package hierarchy at ~/.xemacs/packages. This has changed from simply ~/.xemacs. ... But moving my packages to ~/.xemacs/packages/ was also useless. And, finally, what I met in xemacs-21.2.19/lisp/ChangeLog : 1999-06-24 Michael Sperber [Mr. Preprocessor] <sperber(a)informatik.uni-tuebingen.de> * packages.el (package-locations): Changed default early package hierarchies to ~/.xemacs/mule-packages and ~/.xemacs/xemacs-packages. Now XEmacs picks up my packages on startup. Thanks. Yours, Nick. Recent keystrokes: next next next next next next prior prior next button2 button2up M-x up RET up / * RET button1 button1up button3 misc-user C-x k RET button1 button1up M-x up RET up RET button1 button1up misc-user misc-user misc-user misc-user button1 button1up M-x up RET up left left left left left left left left left left left left left ~ / RET misc-user misc-user misc-user misc-user button2 button2up misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user misc-user button1 button1up misc-user button2 button2up button1 button1up C-x 4 C-g C-x 5 b RET misc-user Recent messages (most recent first): Parsing /home/npakoulin/.mailrc... done Parsing /home/npakoulin/.mailrc... Loading mail-abbrevs...done Loading mail-abbrevs... Loading emacsbug...done Loading emacsbug... C-x 4 C-g not defined. Loading add-log...done Loading add-log... Loading compile...done

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 August 1999