Steve Youngs <youngs(a)xemacs.org&gt; writes: Yup, that's exactly the same I see here on my FreeBSD 4.5 box. Ben, in <3C92DDD2.801031E4(a)666.com&gt; you asked me to can you run with -q, and try (get-language-environment-from-locale "C") but I don't even get this far, sorry for the late answer. norbert.

Norbert Koch <nk(a)viteno.net&gt; writes: [...] I've attached a gdb to a xemacs -vanilla -nw. See below the call stack during the hang. norbert. #0 0xbfbfffa8 in ?? () #1 0x283d943f in _XtWaitForSomething () from /usr/X11R6/lib/libXt.so.6 #2 0x283da924 in XtAppProcessEvent () from /usr/X11R6/lib/libXt.so.6 #3 0x81fd242 in emacs_Xt_next_event (emacs_event=0x8690878) at event-Xt.c:2770 #4 0x80dac00 in event_stream_next_event (event=0x8690878) at event-stream.c:569 #5 0x80dcea7 in next_event_internal (target_event={...}, allow_queued=1) at event-stream.c:2031 #6 0x80dd53b in Fnext_event (event={...}, prompt={...}) at event-stream.c:2252 #7 0x80e37ae in Fnext_command_event (event={...}, prompt={...}) at event-stream.c:2409 #8 0x80cfef2 in Ffuncall (nargs=1, args=0xbfbfee48) at eval.c:3479 #9 0x8097679 in execute_optimized_program ( program=0xbfbfeed4 "Ä\013ÅÆ#\022Ç \021eb\210ÈÉ!\210Ê \020Æ\207ð-(\200UY(¢B\016\b", stack_depth=4, constants_data=0x848ef10) at bytecode.c:744 #10 0x809ae34 in Fbyte_code (instructions={...}, constants={...}, stack_depth={...}) at bytecode.c:2392 #11 0x80cf565 in Feval (form={...}) at eval.c:3281 #12 0x80d4988 in internal_catch (tag={...}, func=0x80cedd4 <Feval>, arg={...}, threw=0x0) at eval.c:1317 #13 0x80981c4 in execute_rare_opcode (stack_ptr=0xbfbff12c, program_ptr=0x877ec39 "\210+rÏÊ!q\210Ð \210\016\";«\005\016\"c\210ÑÈ!)\207\016'ÒÈ\211\211\211\211\030\035\034\036 \e\031\036#\n\205\201", opcode=Bcatch) at bytecode.c:1250 #14 0x809746a in execute_optimized_program ( program=0x877ec10 "\n¬＠\016!?\205Ñ", stack_depth=7, constants_data=0x8487110) at bytecode.c:654 #15 0x8097285 in funcall_compiled_function (fun={...}, nargs=0, args=0xbfbff28c) at bytecode.c:516 #16 0x80cffeb in Ffuncall (nargs=1, args=0xbfbff288) at eval.c:3514 #17 0x8097679 in execute_optimized_program ( program=0x837fd10 "\013A\035ÆÇ\032\031È\r!\025\bÉa«\004Ê \210ËÌ!«\004Í \210ËÌ!«\017ËÎ!«\aÏÐ!\210ª\004Ñ \210\f«\017\016$¬\013ÒÓÔ\f!ÕQ! \210Ö \210*× \210Ø \210ËÙ!«\004Ú \210Û \210rÜÝ!q\210Þ \210ßà!\210\016(áa«\005\016) \210)â ãa«\bä ¬\004å \210æ \210à\026*ä ­\004çÇ!)\207to-autoloads.el\n;;; emacs vernts a ball.\nThe entrance and exit p"..., stack_depth=4, constants_data=0x8487210) at bytecode.c:744 #18 0x8097285 in funcall_compiled_function (fun={...}, nargs=0, args=0xbfbff3ec) at bytecode.c:516 #19 0x80cffeb in Ffuncall (nargs=1, args=0xbfbff3e8) at eval.c:3514 #20 0x8097679 in execute_optimized_program ( program=0x85d7610 "\t«\005ÆÇ!\207È\021ÉÊ!«\tËÌÉÊ!!!\210Í \211\034«\025\fG\rGW«\016Î\r!Î\f!k«\005Ï\f!\025)Ð\r!\025Ñ \210Ò \210\013®\aÉÓ!­\002È\eÔ\b\016\"\"\022\013«\tÕÖ×\n\"Ø\"\210\n¬\004Ù \210Ú\n\016#\016$«\004Ȫ\006\016%­\002Û\016&\013Ü&\006\210Ý \210)Þ \210ß\216à \210)\016'­\003á \207", stack_depth=8, constants_data=0x8487410) at bytecode.c:744 #21 0x8097285 in funcall_compiled_function (fun={...}, nargs=0, args=0xbfbff4d4) at bytecode.c:516 #22 0x80cf7cb in Feval (form={...}) at eval.c:3338 #23 0x80cc767 in condition_case_1 (handlers={...}, bfun=0x80cedd4 <Feval>, barg={...}, hfun=0x80a847c <cmd_error>, harg={...}) at eval.c:1692 #24 0x80a8504 in top_level_1 (dummy={...}) at cmdloop.c:208 #25 0x80d4988 in internal_catch (tag={...}, func=0x80a84d4 <top_level_1>, arg={...}, threw=0x0) at eval.c:1317 #26 0x80a7703 in initial_command_loop (load_me={...}) at cmdloop.c:287 #27 0x80c85e1 in xemacs_21_5_b5_i386_unknown_freebsd4_5 (argc=3, argv=0xbfbff8f0, envp=0xbfbff900, restart=0) at emacs.c:2312 #28 0x80ca529 in main (argc=3, argv=0xbfbff8f0, envp=0xbfbff900) at emacs.c:2749 #29 0x80830dd in _start ()

On Sunday 17 March 2002 09:27 am, William M. Perry wrote: I get a locked up console when I try to run sans $DISPLAY. I should have said something, but the system at work where I first saw this is suspect in its own right. I have now verified this on my old reliable here at home. -- STH

|--==> "WMP" == William M Perry <wmperry(a)gnu.org&gt; writes: WMP> Steve Youngs <youngs(a)xemacs.org&gt; writes: WMP> I saw this just yesterday in the GTK build and thought it was GTK related. WMP> Are you building just with TTY support? X11? GTK? I let TTY and X11 auto-detect, and use '--with-gtk=no' and '--with-gnome=no'. Here's the complete set of configure options I use: ./configure \ --extra-verbose \ --dynamic=yes \ --with-gtk=no \ --with-gnome=no \ --with-toolbars=yes \ --with-wmcommand=yes \ --with-athena=next \ --with-menubars=lucid \ --with-scrollbars=athena \ --with-dialogs=athena \ --with-widgets=athena \ --with-png=yes \ --with-sound=native,noesd \ --with-modules \ --with-site-lisp=yes \ --with-site-modules=yes \ --pdump \ --with-mule \ --debug \ --error-checking=all \ --memory-usage-stats \ --use-union-type \ --with-clash-detection \ --site-libraries=/usr/local/pgsql/lib -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|

|--==> "APA" == Adrian Aichner <Adrian.Aichner(a)t-online.de&gt; writes: SY> Running XEmacs from a console in Linux, it'll load up, but that's all SY> it will do. Press any key once it's loaded and it just sits there SY> frozen solid. The only way out is to switch to another console and SY> kill the xemacs process. SY> No core files are generated, any idea how I can help you debug this SY> one? APA> Does it read .emacs? Yes. Actually it's '~/.xemacs/init.el', but I know what you mean. :-) APA> Does C-g help? No. APA> Or C-g C-g, perhaps? No. APA> If yes, how about APA> (setq debug-on-signal t) APA> (setq debug-on-quit t) APA> and then (when in appears to hang) C-g or even C-g C-g. I'll try, let you know what happens. -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|

|--==> "BW" == Ben Wing <ben(a)666.com&gt; writes: BW> ok, i can duplicate this too. i'll look at it tomorrow, since it's BW> bedtime now. BW> it probably is related to the modeline changes i recently made -- BW> there's some stuff to print the tty frame number if it's greater than BW> 1, done in a clever [or hackish, you be the judge] way. BW> someone might try disabling that code -- it's in modeline.el -- and BW> seeing if that fixes the problem. I commented out: (defconst modeline-tty-frame-specifier (make-specifier 'boolean)) (add-hook 'create-frame-hook 'modeline-update-tty-frame-specifier) (defun modeline-update-tty-frame-specifier (f) (if-fboundp 'frame-tty-p (if (and (frame-tty-p f) (> (frame-property f 'frame-number) 1)) (set-specifier modeline-tty-frame-specifier t f)))) (define-modeline-control tty-frame-id (list modeline-tty-frame-specifier " [%S]" ) "Modeline control for showing which TTY frame is selected.") and: (cons modeline-tty-frame-id-extent 'modeline-tty-frame-id) Which is what you are talking about isn't it? Sorry, didn't make any difference.:-( -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|