Re: [CRASH] in -nw mode / image specifiers

Andy> Do you have the config that is causing this (Xdefaults?) OK, I'm seeing the same thing; I _can_ run under gdb, so if you have experiments you want me to try, let me know. I have no XEmacs-relevant X configuration or Xdefaults. Fairly recent 21.2.36. Running -vanilla -nw. Under gdb, I get the same C stack trace (minus the bottom two frames, which are abort handling in libc, I guess?) as from the core dump. The C backtrace is the same as Didier's, subject to some variations in the addresses. I also see the pixmap file name as the argument to query_string_geometry. Lisp backtrace follows: # (unwind-protect ...) # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque-ptr, adr=0x83c7f7c) 0x83ee798> ...) # (unwind-protect ...) # bind (inhibit-quit) split-window(nil nil) # bind (old-w old-point size window-full-p new-w bottom moved arg) split-window-vertically(nil) # bind (command-debug-status) call-interactively(split-window-vertically) # (condition-case ... . error) # (catch top-level ...) Program received signal SIGSEGV, Segmentation fault. 0x40395dc1 in kill () from /lib/libc.so.6 -- 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."