Re: Seg fault in Xemacs 21.1.14 on X with Mandrake Linux 8.2 i386

rpgoldman> I apologize for not using either of the prescribed rpgoldman> methods of bug reporting, per the message but: rpgoldman> 1. My xemacs tarball didn't come with a send-pr script rpgoldman> per the message. rpgoldman> 2. I couldn't get the X version to run, so couldn't rpgoldman> get at the help rpgoldman> menu to use the Submit Bug Report item. rpgoldman> When I start up my Xemacs normally (i.e., under X) I rpgoldman> always get a seg fault. Using xemacs -nw, everything rpgoldman> is hunky-dory. rpgoldman> I'm attaching all the information you ask for; if rpgoldman> there's something else I should collect, please let me rpgoldman> know. Thanks rp, for the detailed feedback. You can generate the bug report in xemacs -nw as well. Just hold down Meta (often labelled Alt) while hitting the letter x. Then type report-emacs-bug at the M-x prompt. You can then save the buffer contents to a file, and send them off with your Mutt MUA. This will provide us even some more information. Thanks in advance, Adrian rpgoldman> Best, rpgoldman> r rpgoldman> Here's the backtrace: rpgoldman> Lisp backtrace follows: rpgoldman> # bind (frame-being-created) rpgoldman> make-frame(nil #<x-device on ":0.0" 0x1a14>) rpgoldman> frame-initialize() rpgoldman> # bind (debugger debug-on-error command-line-args-left) rpgoldman> command-line() rpgoldman> # (unwind-protect ...) rpgoldman> normal-top-level() rpgoldman> # (condition-case ... . error) rpgoldman> # (catch top-level ...) rpgoldman> Segmentation fault (core dumped) rpgoldman> C stack backtrace: rpgoldman> (gdb) where rpgoldman> #0 0x40322621 in kill () from /lib/libc.so.6 rpgoldman> #1 0x080a0de0 in fatal_error_signal (sig=11) at emacs.c:264 rpgoldman> #2 0x40322478 in killpg () from /lib/libc.so.6 rpgoldman> #3 0x4015cc0a in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6 rpgoldman> #4 0x4015dab9 in XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6 rpgoldman> #5 0x0814e3c0 in x_create_widgets (f=0x83eb4c8, lisp_window_id=136920004, rpgoldman> parent=136920004) at frame-x.c:1952 rpgoldman> #6 0x0814f481 in x_init_frame_1 (f=0x83eb4c8, props=136920004) rpgoldman> at frame-x.c:2183 rpgoldman> #7 0x080ea16b in Fmake_frame (props=136920004, device=137134816) rpgoldman> at frame.c:383 rpgoldman> #8 0x080a467c in funcall_recording_as (recorded_as=137016252, nargs=2, rpgoldman> args=0xbfffeb30) at eval.c:3197 rpgoldman> #9 0x080a80c6 in Ffuncall (nargs=3, args=0xbfffeb30) at eval.c:3238 rpgoldman> #10 0x08084fb8 in Fbyte_code (bytestr=136179784, vector=136179856, maxdepth=11) rpgoldman> at bytecode.c:416 rpgoldman> #11 0x080a5460 in funcall_lambda (fun=136179944, nargs=0, rpgoldman> arg_vector=0xbfffee64) at eval.c:3607 rpgoldman> #12 0x080a4789 in funcall_recording_as (recorded_as=137396188, nargs=0, rpgoldman> args=0xbfffee60) at eval.c:3214 rpgoldman> #13 0x080a80c6 in Ffuncall (nargs=1, args=0xbfffee60) at eval.c:3238 rpgoldman> #14 0x08084fb8 in Fbyte_code (bytestr=136315060, vector=136315176, maxdepth=9) rpgoldman> at bytecode.c:416 rpgoldman> #15 0x080a5460 in funcall_lambda (fun=136315396, nargs=0, rpgoldman> arg_vector=0xbffff294) at eval.c:3607 rpgoldman> #16 0x080a4789 in funcall_recording_as (recorded_as=137482240, nargs=0, rpgoldman> args=0xbffff290) at eval.c:3214 rpgoldman> #17 0x080a80c6 in Ffuncall (nargs=1, args=0xbffff290) at eval.c:3238 rpgoldman> #18 0x08084fb8 in Fbyte_code (bytestr=136312932, vector=136313116, maxdepth=13) rpgoldman> at bytecode.c:416 rpgoldman> #19 0x080a5460 in funcall_lambda (fun=136313636, nargs=0, rpgoldman> arg_vector=0xbffff380) at eval.c:3607 rpgoldman> #20 0x080a4fcc in apply_lambda (fun=136313636, numargs=0, rpgoldman> unevalled_args=136920004) at eval.c:3511 rpgoldman> #21 0x080a4149 in Feval (form=137321548) at eval.c:3085 rpgoldman> #22 0x080a211e in condition_case_1 (handlers=136920116, rpgoldman> bfun=0x80a36e0 <Feval>, barg=137321548, hfun=0x808b9a0 <cmd_error>, rpgoldman> harg=136920004) at eval.c:1653 rpgoldman> #23 0x0808bb0f in top_level_1 (dummy=136920004) at cmdloop.c:206 rpgoldman> #24 0x080a1fea in internal_catch (tag=136994376, func=0x808bae0 <top_level_1>, rpgoldman> arg=136920004, threw=0x0) at eval.c:1328 rpgoldman> #25 0x0808b304 in initial_command_loop (load_me=136920004) at cmdloop.c:285 rpgoldman> #26 0x0809f977 in xemacs_21_1_14_i386_Mandrake_linux () at emacs.c:1725 rpgoldman> #27 0x080a0030 in main (argc=1, argv=0xbffff8a4, envp=0xbffff8ac) rpgoldman> at emacs.c:2142 rpgoldman> #28 0x40310280 in __libc_start_main () from /lib/libc.so.6 rpgoldman> Here's the installation description: rpgoldman> uname -a: Linux tsathoggua.mydomain 2.4.18-6mdksmp #1 SMP Fri Mar 15 01:24:36 C\ET 2002 i686 unknown rpgoldman> ./configure '--prefix=/usr' 'i386-Mandrake-linux' rpgoldman> XEmacs 21.1.14 "Cuyahoga Valley" configured for `i386-Mandrake-linux'. rpgoldman> Where should the build process find the source code? /home/rpg/src/xemacs/\xemacs-21.1.14 rpgoldman> What installation prefix should install use? /usr rpgoldman> What operating system and machine description files should XEmacs use? rpgoldman> `s/linux.h' and `m/intel386.h' rpgoldman> What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno\-switch rpgoldman> Should XEmacs use the GNU version of malloc? yes rpgoldman> (Using Doug Lea's new malloc from the GNU C Library.) rpgoldman> Should XEmacs use the relocating allocator for buffers? yes rpgoldman> What window system should XEmacs use? x11 rpgoldman> Where do we find X Windows header files? /usr/X11R6/include rpgoldman> Where do we find X Windows libraries? /usr/X11R6/lib rpgoldman> Compiling in support for XAUTH. rpgoldman> Compiling in support for XPM images. rpgoldman> Compiling in support for PNG image handling. rpgoldman> Compiling in support for (builtin) GIF image handling. rpgoldman> Compiling in support for JPEG image handling. rpgoldman> Compiling in support for TIFF image handling. rpgoldman> Compiling in support for X-Face message headers. rpgoldman> Compiling in native sound support. rpgoldman> Compiling in support for ncurses. rpgoldman> Compiling in support for proper session-management. rpgoldman> Using Lucid menubars. rpgoldman> Using Lucid scrollbars. rpgoldman> Using Athena dialog boxes. rpgoldman> Compiling in DLL support. rpgoldman> movemail will use "dot-locking" for locking mail spool files. rpgoldman> Using Lisp_Objects with minimal tagbits. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/