May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

`make-mswindows-device' crashes Cygwin32 21.0B41 26 years, 6 months

Paul Stodghill

In XEmacs 21.0 "San Clemente" [Lucid] (i386-pc-cygwin32) of Tue May 26 1998 on MAPLE configured using `configure --site-includes=/usr/local/include --site-libraries=/usr/local/lib' I'm still trying to figure out how to get Cygwin32 GDB to run, so I can't provide further information at the moment.... maple% uname -a CYGWIN32_NT MAPLE 4.0 19.2 i686 unknown maple% printenv DISPLAY 127.0.0.1:0.0 maple% /usr/local/bin/xemacs-21.0-b41.exe -vanilla -f make-mswindows-device Fatal error: assertion failed, file event-unixoid.c, line 153, CONSOLE_TTY_P (con) Fatal error (6). Your files have been auto-saved. Use `M-x recover-session' to recover them. Please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /usr/local/bin/xemacs-21.0-b41.exe core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: make-device(mswindows nil) make-mswindows-device() # bind (arg) command-line-do-funcall("-f") # bind (dir file-count line end-of-options first-file-buffer file-p arg tem) command-line-1() # bind (command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Abort maple%

2 participants
1 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 26 years, 6 months

Michael Sperber

>>>>> "Didier" == Didier Verna <verna(a)inf.enst.fr> writes: Didier> Hrvoje Niksic <hniksic(a)srce.hr> writes: >> > ~/.xemacs-packages. >> >> Yes yes yes! Agreed 100%. Didier> No! Let's use ~/.xemacs/packages, and ~/.xemacs/whatever-else for the Didier> user. It's more consistent with the fact of having .../lib/xemacs, and Didier> .../lib/xemacs/packages for the packages. [Chuckle ...] Actually, the official location for the late packages is .../lib/xemacs/xemacs-packages. (You don't know that because the documentation hasn't been written yet.) So, consistency would dictate either ~/.xemacs-packages or ~/.xemacs/xemacs-packages. Steve, you get to decide, I guess. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 26 years, 6 months

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > > ~/.xemacs-packages. > > Yes yes yes! Agreed 100%. No! Let's use ~/.xemacs/packages, and ~/.xemacs/whatever-else for the user. It's more consistent with the fact of having .../lib/xemacs, and .../lib/xemacs/packages for the packages. --Didier

1 participants
0 comments

Re: [CRASH] 21.0-b41 on i686-pc-linux/Redhat5.0 26 years, 6 months

Aki Vehtari

Ave> chaos 13:14 % gdb src/xemacs core Ave> ... Ave> Core was generated by `src/xemacs -vanilla'. Ave> Program terminated with signal 11, Segmentation fault. Ave> #0 0x40359661 in ?? () Ave> (gdb) where Ave> #0 0x40359661 in ?? () Ave> Cannot access memory at address 0xbfffea18. Stupid me, coredumpsize limit was unusually small... Here's new one... chaos 16:06 % gdb src/xemacs core Core was generated by `src/xemacs -vanilla'. Program terminated with signal 11, Segmentation fault. find_solib: Can't read pathname for load map: Input/output error #0 0x40359661 in ?? () from /lib/libc.so.6 (gdb) where #0 0x40359661 in ?? () from /lib/libc.so.6 #1 0x80b1c9c in fatal_error_signal (sig=11) at emacs.c:262 #2 0xbfffeb14 in ?? () #3 0x81d96dd in size_menu (mw=0x0, level=0) at xlwmenu.c:2025 (gdb)

1 participants
0 comments

GC and Lstream ( Was Finally a crash again....) 26 years, 6 months

Jan Vroonhof

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > #11 0x2f5b14 in symbol_value_in_buffer () > #12 0x236cfc in buffer_insert_string_1 () > #13 0x237d6c in buffer_insert_raw_string_1 () > #14 0x2675b8 in lisp_buffer_writer () > #15 0x263218 in Lstream_flush_out () > #16 0x2632c0 in Lstream_flush () > #17 0x2632c0 in Lstream_flush () > #18 0x2629b4 in finalize_lstream () > #19 0x61b84 in garbage_collect_1 () Ugh... It seems to me that somehow the buffer argument in a lisp-buffer lstream is not GC protected enough? Are there any tips in handling a core file without symbols? Jan

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 26 years, 6 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Yes yes yes! Agreed 100%. > > -> .xemacs-packages/ for personal packages Why not .xemacs/packages ? There is no need to have two directories > -> .xemacs/ (if exists) for init files, otherwise various ~/.foo > files... I still fail to see why all these various .foo files (or there .el equivalents) cannot be placed in the standard loadpath, but that is just me I guess. Jan

1 participants
0 comments

Re: custom-file 26 years, 6 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > > Which is OK. It just that I want the default to be WITH .xemacs. > > Now I'm confused. You never want a .xemacs dir which is fine. It just means you need a (setq custom-file "~/.xemacs-custom") in your .emacs. Jan P.S. This IS all 21.1 stuff we are talking about is it? 21.0 will unfortunately have its customizations still in .emacs?

1 participants
0 comments

Sounds -- .au, .wav, or both? 26 years, 6 months

SL Baur

What should be done about sounds? It's been rumored that MS Windows doesn't grok .au -- XEmacs/Linux (and I presume BSD) sound support handles both .wav and .au so I don't particularly care either way. They probably should be put in a package, regardless. Is there any platform that absolutely requires .au and cannot handle .wav? If we need both, it will definitely have to be a package and we'll have to upgrade the sound playing code to have lists of valid extensions so that `play-sound-file' can Do The Right Thing and either play "im_so_happy.au" or "im_so_happy.wav" as the situation warrants. I like sound (a lot); I consider this an issue that needs to be resolved prior to release.

4 participants
8 comments

Re: XEmacs on NT: Personal experience 26 years, 6 months

Hrvoje Niksic

Andy Piper <andyp(a)parallax.co.uk> writes: > >* The toolbars are ugly black-and-white, with the ugly-looking > > captions. However, my XEmacs does appear to have XPM support (I was > > able to see gnus.xpm properly). Does anyone have a clue why this is > > so? > > Huh? I get greyscale toolbars which is what you get under > unix. There is no xbm support so the standard B&W toolbars are > impossible. OK, maybe what I saw were downsized toolbars, which made them look ugly? I'm not sure if they're b&w or greyscale, but they sure are ugly as hell! > >* Continuation glyphs are characters instead of glyphs. This > > should be quite easy to fix -- those glyphs are b&w. > > I think these are xbm and hence not implemented. They need to be > converted to xpm. Hmph. > >* Toolbars are displaying balloon-help (tooltips) by default. This is > > nice, but: > > > > - Will it clash with the people currently using the `balloon-help' > > Lisp package; > > Does it work under nt? I forgot to try it. > >* Whoever thought of that default size should be ＠#$＠!#$#＠$! :-) > > (frame-width) says 78, and (frame-height) says 18. Horrible. > > Yes! I'm hoping this will get fixed one way or another. And the above value is wrong. What I actually get is 71 x 19! > >* Certain menubar items don't work, or don't do anything useful. This > > should be polished before the release. Examples: > > - Font menu > > This will not be fixed for 21.0. Yeah, but it should be removed from the menu under Windows, if it does not work. That's all I meant. > >* The docstrings were missing. This is probably a deficiency of > > Fabrice's distribution. Also, I wasn't able to send out a mail due > > to lack of `fakemail'. > > You can use smtpmail. Then it should be set up by default... -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "Psychos _do not_ explode when sunlight hits them."

4 participants
4 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 26 years, 6 months

Hrvoje Niksic

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > If you guys put random stuff in there, I promise something will > break eventually. It does not belong there. Ever. Period. The > only way to use ~/.xemacs for random init goop would be to put the > default early package hierarchy somewhere else. Maybe > ~/.xemacs-packages. Yes yes yes! Agreed 100%. -> .xemacs-packages/ for personal packages -> .xemacs/ (if exists) for init files, otherwise various ~/.foo files... -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Predestination was doomed from the start.

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 May 1998