May 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: 21.2.34 crash on Solaris 2.7 23 years, 10 months

Jan Vroonhof

Raymond Toy <toy(a)rtp.ericsson.se> writes: > file and I thought it was swapping). I did have ilisp and a cmulisp > and gdb process going at the time. > > #2 0xfeb392a4 in ?? () > #3 0xa775c in Fdump_emacs (intoname=3053572, symname=3053572) at emacs.c:2842 > #4 0x692f0 in make_lcrecord_list (size=0, implementation=0x0) at alloc.c:2259 You are right. This stack trace is weird... Jan

1 participants
0 comments

lwlib expertise anyone? Menubar construction... 23 years, 10 months

William M. Perry

The menubar in the GTK port is flashing a lot more than I like when switching buffers temporarily. I couldn't quite figure out why the lwlib menus did not update as frequently. Basically, in menubar-gtk.c, there is a function called menu_create_menubar() that converts a menubar description into appropriate GTK widgets. It first deletes everything in the current menubar, then gcpros the callbacks, and then creates the actual top-level menu items. The X specific code just creates the widget_value list... does lwlib do something smart like delay the creation of the menu until the next redisplay? set_frame_menubar seems to get called _VERY_ often, even when inside a save-excursion. The main offenders seem to be mouse-motion over the grep or speedbar buffers. Thanks! -Bill P. PS: The GTK port is pretty damn solid now if anyone wants to check it out. Toolbars, menubars, scrollbars, drag&drop, etc. Only major thing left is that selection handling sucks. I modelled it after the windows version, but it appears that confuses people used to the X behaviour. Oh well, I guess I'll have to rewrite it to be more x-like.

1 participants
0 comments

Re: set-window-configuration vs error-checking sub windows 23 years, 10 months

Jan Vroonhof

Andy Piper <andy(a)xemacs.org> writes: > Here's what I think is happening. The instantiator changes due to someone > clicking on a tab, Note that I did not click on any tab. However the selected buffer changed. Before we do any fancy thing to keep the two caches consistent (such as creating a "cached_image_instance" object that proxys for image_instances, but has a finalizer that removes it from the frame cache). How about trying to get rid of the frame cache alltogether? AFAICS the frame cache is only used in the loops in redisplay_unmap_subwindow and find_matching_subwindow. Can they be replaced by a loop over all windows followed by a map over their caches? Jan

2 participants
1 comments

http://www.xemacs.org/list-archives/xemacs-* are all down 23 years, 10 months

Adrian Aichner

XEmacs mailing list archives cannot be accessed as of this writing. Adrian Here's the error I get for xemacs-patches: Archive Directory Error Opening directory '/opt/http-xemacs/docs/list-archives/xemacs-patches' for list 'xemacs-patches' received the error 'No such file or directory' XEmacs List Manager -- Adrian Aichner <adrian(a)xemacs.org>

3 participants
3 comments

21.2.34 crash on Solaris 2.7 23 years, 10 months

Raymond Toy

Haven't see this one before. I think there's some stack corruption going on. I had a single frame up and was typing some keys (sorry, don't remember what because it took a while for xemacs to produce a core file and I thought it was swapping). I did have ilisp and a cmulisp and gdb process going at the time. Anyway, the C traceback is appended. The lisp backtrace is in kernel memory somewhere waiting to be flushed out... Ray #0 0xfeb96870 in ?? () #1 0xfeb95990 in ?? () #2 0xfeb392a4 in ?? () #3 0xa775c in Fdump_emacs (intoname=3053572, symname=3053572) at emacs.c:2842 #4 0x692f0 in make_lcrecord_list (size=0, implementation=0x0) at alloc.c:2259 #5 0x6ae14 in garbage_collect_1 () at alloc.c:3335 #6 0xae704 in Feval (form=3053572) at eval.c:3009 #7 0x796c4 in execute_optimized_program (program=0xffbed244 "", stack_depth=2, constants_data=0x97cb90) at bytecode.c:649 #8 0x78f20 in bytecode_arithop (obj1=2842624, obj2=3053572, opcode=4290696348) at bytecode.c:403 #9 0xaeab0 in Feval (form=-4271096) at eval.c:3083 #10 0x796c4 in execute_optimized_program (program=0xffbed494 "", stack_depth=1, constants_data=0x97cb10) at bytecode.c:649 #11 0x78f20 in bytecode_arithop (obj1=3838796, obj2=3838796, opcode=4290696936) at bytecode.c:403 #12 0xaeab0 in Feval (form=3053596) at eval.c:3083 #13 0xafb4c in run_hook_with_args_in_buffer (buf=0x6159cc, nargs=3055108, args=0xd749c4, cond=2868224) at eval.c:3646 #14 0x6d194 in print_buffer (obj=14109124, printcharfun=3053596, escapeflag=2895872) at buffer.c:266 #15 0x6d81c in push_buffer_alist (name=14109124, buf=14109124) at buffer.c:507 #16 0xbc858 in Ftest_data_format_conversion () at tests.c:406 #17 0x165ec0 in Fmove_to_column (column=11746816, force=27569, buffer=2549760) at indent.c:473 #18 0x1661c4 in vmotion_1 (w=0x2bc400, orig=27569, vtarget=-4269296, ret_vpos=0x2e9804, ret_vpix=0x0) at indent.c:663 #19 0x166e3c in charcount_to_bytecount (ptr=0xb33e00 "\030\2230", len=-1) at insdel.c:389 #20 0x89a74 in internal_self_insert (c1=10, noautofill=0) at buffer.h:647 #21 0x893a0 in Fbeginning_of_line (n=0, buffer=0) at cmds.c:165 #22 0xae8d0 in Feval (form=21) at lisp.h:591 #23 0x796c4 in execute_optimized_program (program=0xffbedd1c "", stack_depth=1, constants_data=0x3ea410) at bytecode.c:649 #24 0x78f20 in bytecode_arithop (obj1=2842624, obj2=3053572, opcode=4290699136) at bytecode.c:403 #25 0xaeab0 in Feval (form=2816000) at eval.c:3083 #26 0x796c4 in execute_optimized_program (program=0xffbedf7c "", stack_depth=0, constants_data=0x43e3f0) at bytecode.c:649 #27 0x78f20 in bytecode_arithop (obj1=2842624, obj2=3053572, opcode=4290699728) at bytecode.c:403 #28 0xaeab0 in Feval (form=3152956) at eval.c:3083 #29 0x796c4 in execute_optimized_program (program=0xffbee1cc "", stack_depth=0, constants_data=0x9f6790) at bytecode.c:649 #30 0x78f20 in bytecode_arithop (obj1=2842624, obj2=3053572, opcode=4290700552) at bytecode.c:403 #31 0xaeab0 in Feval (form=0) at eval.c:3083 #32 0x7e2b4 in Fcall_interactively (function=10254188, record_flag=3053572, keys=3053572) at lisp.h:591 #33 0xad2d8 in signal_wrong_number_of_arguments_error (function=10146916, nargs=3053572) at eval.c:2041 #34 0x1023e8 in push_recent_keys (event=4751104) at event-stream.c:3607 #35 0x102d68 in pre_command_hook () at event-stream.c:3885 #36 0x885dc in Frecursive_edit () at lisp.h:591 #37 0x88370 in recursive_edit_unwind (buffer=3053572) at lisp.h:591 #38 0xaa9a0 in Fmacroexpand_internal (form=2818048, env=557860) at eval.c:1225 #39 0x888cc in Fcommand_loop_1 () at cmdloop.c:495

1 participants
0 comments

AIX heads up with -b34 tree... 23 years, 10 months

Valdis Kl=?iso8859-4?Q?=BA?=tnieks

The 'ibmcxx.cmp 3.6.6.3' appears to miscompile at least 2 different XEmacs source files (fileio.c and at least one other) when using '-O3 -qstrict'. 3.6.6.2 appears to be fine, as does compiling with -g. The fileio.c botch is the cause of the crash I saw loading thai-xtix.el. The other one causes a ugly crash while starting up. Only recommendation I can make is to use 3.6.6.2. I'll post a patch for PROBLEMS soon as I figure out what I think it should say ;) /Valdis

1 participants
0 comments

Re: 21.2.34 crash 23 years, 10 months

Raymond Toy

>>>>> "Nick" == Nick V Pakoulin <npak(a)kazbek.ispras.ru> writes: Nick> Andy Piper <andy(a)xemacs.org> writes: >> At 03:41 PM 5/30/00 +0400, Nick V. Pakoulin wrote: >> >My newly built 21.2.34 crashed while spell checking. No LISP trace, >> sorry, but >> >> Please update from CVS - it should be fixed. >> Nick> I'd love to, but I'm behind a firewall with the CVS ports closed ;(( I also have a crash on my Solaris box very similar to yours. I'm also behind a firewall, but socks and ssh appears to work here (at least I can get CVS access to sourceforge things). I followed the directions for CVS updating from cvs.xemacs.org, but when I try to login according to the directions, I get the error "Unknown host cvs.xemacs.org". Am I missing something? Ray

1 participants
0 comments

Re: 21.2.34 crash 23 years, 10 months

Nick V. Pakoulin

Andy Piper <andy(a)xemacs.org> writes: > At 03:41 PM 5/30/00 +0400, Nick V. Pakoulin wrote: > >My newly built 21.2.34 crashed while spell checking. No LISP trace, > sorry, but > > Please update from CVS - it should be fixed. > I'd love to, but I'm behind a firewall with the CVS ports closed ;(( > andy Nick > -------------------------------------------------------------- > Dr Andy Piper > Principal Consultant, BEA Systems Ltd

1 participants
0 comments

Problem with PCL-CVS 2.9.9 in sumo tarball 23 years, 10 months

Nick V. Pakoulin

I downloaded and installed xemacs-sumo-2000-05-24.tar.gz. PCL-CVS is release v2_9_9. I used `cvs-status' to get *cvs* buffer, then tried to get status of a file via `cvs-mode-status' and got the error : Cannot open load file: mule The backtrace is: Signaling: (file-error "Cannot open load file" "mule") load-internal("mule" nil t nil nil nil) load("mule" nil t nil) require(mule) load-internal("cvs-status" nil nil nil nil nil) load("cvs-status" nil nil nil) cvs-status-mode() cvs-temp-buffer("status") cvs-mode-do("status" nil nil :dont-change-disc t :show t :postproc nil) #<compiled-function nil "...(19)" [cvs-mode-do "status" flags nil :dont-change-disc t :show :postproc cvs-auto-remove-handled status (...)] 11>() #<compiled-function nil "...(15)" [commandp -cvs-mode!-fun call-interactively] 2>() cvs-mode!(#<compiled-function nil "...(19)" [cvs-mode-do "status" flags nil :dont-change-disc t :show :postproc cvs-auto-remove-handled status (...)] 11>) #<compiled-function (flags) "...(4)" [cvs-mode! #<compiled-function nil "...(19)" ... 11>] 2 ("/usr/local/lib/xemacs/xemacs-packages/lisp/pcl-cvs/pcl-cvs.elc" . 49665) (list (cvs-flags-query ... "cvs status flags"))>(nil) call-interactively(cvs-mode-status) So thought a little bit and recompiled pcl-cvs. MAGIC happenned!!! ;))) Now it WORKS 8-)) Funny, egh ? Nick.

1 participants
0 comments

21.2.34 crash 23 years, 10 months

Nick V. Pakoulin

My newly built 21.2.34 crashed while spell checking. No LISP trace, sorry, but there is C one: #0 0x403034e1 in __kill () from /lib/libc.so.6 #1 0x80aff0e in fatal_error_signal (sig=6) at emacs.c:514 #2 0x40303408 in __restore () at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127 #3 0x40304868 in abort () at ../sysdeps/generic/abort.c:88 #4 0x80afe28 in assert_failed (file=0x81fd3d0 "glyphs.c", line=590, expr=0x81fd484 "DOMAIN_LIVE_P (instance)") at emacs.c:3114 #5 0x8114106 in check_image_instance_structure (instance=143632224) at glyphs.c:590 #6 0x811ba36 in unmap_subwindow (subwindow=143632224) at glyphs.c:4425 #7 0x811b64d in reset_frame_subwindow_instance_cache (f=0x8540a60) at glyphs.c:4193 #8 0x81b28f8 in Fset_window_configuration (configuration=142184696) at window.c:5222 #9 0x81b4cce in save_window_excursion_unwind (window_config=142184696) at window.c:5789 #10 0x80b6910 in unbind_to_hairy (count=22) at eval.c:4654 #11 0x80b8881 in unbind_to (count=22, value=136794628) at eval.c:4629 #12 0x8090251 in execute_rare_opcode (stack_ptr=0xbffff194, program_ptr=0x890ae1c "\210\016\f?╜\006\016\r╝\002н*\207", opcode=Bsave_window_excursion) at bytecode.c:1241 #13 0x808f738 in execute_optimized_program ( program=0x890adf8 "\b╛\004а \210б\216\212цд\reU╚\013\016\006dU╚\005г ╙\002х\ 016\t╝\002й#\210к\213\210\016\f?╜\006\016\r╝\002н*\207", stack_depth=4, constants_data=0x87c93e0) at bytecode.c:657 #14 0x808f559 in funcall_compiled_function (fun=144300576, nargs=2, args=0xbffff294) at bytecode.c:519 #15 0x80b472f in Ffuncall (nargs=3, args=0xbffff290) at eval.c:3249 #16 0x808f8f4 in execute_optimized_program ( program=0x898dd10 "\212eb\210юаб\013!дQеф#\036\aх\016\a╝\tюиеф#╝\002e!\036\nх\016\013╛\004d╙\eл\016\013!╚\020ю\016\013еф#╚\005м\224╙\td╙\006d\016\013 ^!\036\016оп!╚\013\016\020╚\aя\016\020!╙\002р\036\023ту!╚\016жв ьыя\016\032!╟\005╙Xтш!╚\016ж\016\027ьыя\016\032!╟\005╙F\016\034щk╛\a\016\034чk╚\016ъыЮы\016!ы\016\023╟\a╙-\016\034Бk╚\nЦыя\016$!Q╙\036\016\a╛\nЕыФыГ╟\005╙\021оХ!╚\nЦыя\016(!Q╙\003\016\023\036)Й\016)ьQК"..., stack_depth=8, constants_data=0x897cab8) at bytecode.c:747 #17 0x808f559 in funcall_compiled_function (fun=144301136, nargs=0, args=0xbffff3b8) at bytecode.c:519 #18 0x80b472f in Ffuncall (nargs=1, args=0xbffff3b4) at eval.c:3249 #19 0x80b7c04 in apply1 (fn=144301136, arg=136794628) at eval.c:3832 #20 0x8092a5e in Fcall_interactively (function=138872684, record_flag=136794628, keys=136794628) at callint.c:394 #21 0x80b45da in Ffuncall (nargs=2, args=0xbffff5a4) at eval.c:3214 #22 0x808f8f4 in execute_optimized_program ( program=0x87ce198"ю\t!╛\006бц\f\"\210е\t!\210ф\t!\036\aх\016\a!╜1и\016\a!╜+й\016\a!╜%й\016\a!\211\036\013\024л\016\013!╚\022м\016\013!╚\aн\016\013!╙\n\016\ 013 ╙\005о\016\013!))\207©1", stack_depth=4, constants_data=0x8424e80) at bytecode.c:747 #23 0x808f559 in funcall_compiled_function (fun=138483860, nargs=1, args=0xbffff6a8) at bytecode.c:519 #24 0x80b472f in Ffuncall (nargs=2, args=0xbffff6a4) at eval.c:3249 #25 0x809413e in Fcall_interactively (function=138231684, record_flag=136794628, keys=136794628) at callint.c:946 #26 0x80b31c7 in Fcommand_execute (cmd=138231684, record=136794628, keys=136794628) at eval.c:2652 #27 0x80e5643 in execute_command_event (command_builder=0x8442090, event=144706500) at event-stream.c:3838 #28 0x80e611e in Fdispatch_event (event=144706500) at event-stream.c:4205 #29 0x809864d in Fcommand_loop_1 () at cmdloop.c:579 #30 0x809887d in command_loop_1 (dummy=136794628) at cmdloop.c:494 #31 0x80b879a in condition_case_1 (handlers=136794724, bfun=0x8098848 <command_loop_1>, barg=136794628, hfun=0x8097c70 <cmd_error>, harg=136794628) at eval.c:1640 #32 0x809895c in command_loop_2 (dummy=136794628) at cmdloop.c:256 #33 0x80b866f in internal_catch (tag=136866388, func=0x8098924 <command_loop_2>, arg=136794628, threw=0x0) at eval.c:1306 #34 0x8097fed in initial_command_loop (load_me=136794628) at cmdloop.c:305 #35 0x80ae3a2 in xemacs_21_2_b34_i686_pc_linux (argc=5, argv=0xbffffbc4, envp=0xbffffbdc, restart=0) at emacs.c:2146 ------------------------------------------------------------------------------- Built info: uname -a: Linux hookah 2.2.13-13abit #1 Wed Feb 23 16:53:10 CST 2000 i686 unknown ./configure '--with-pop' XEmacs 21.2-b34 "Molpe" configured for `i686-pc-linux'. Compilation / Installation: Source code location: /local/src/xemacs-21.2.34 Installation prefix: /usr/local 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. 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. Compiling in support for X-Face message headers. 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 PostgreSQL. - PostgreSQL headers location: pgsql Internationalization: Mail: Compiling in support for POP mail retrieval. 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: --------------------------------------------------------- ------------------------------------------------------------------------------- Hope to see stable XEmacs soon ;) Nick.

2 participants
1 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 May 2000