May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[Failure] xemacs-21.0-b41 memory faults on Digital UNIX 4.0 26 years, 6 months

Kevin Oberman

This should come as no surprise, but 21.0-b41 still dumps core (as did b40) when built on DU4.0D with CDE. I compiled with both gcc 2.8.1. and cc and configured with --use-union-type. Both fail in the same manner. cc build went fine except for frame.c for which the compiler reported an internal error. (I built frame with gcc.) With gcc, when I tried to compile with the default -O3, things went very badly with pages and pages of warnings about incorrect data types. Building -O2 fixed these. There were still several warnings about pointer to integer casts: gcc -c -g -O2 -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -D_BSD -I/usr/dt/include event-unixoid.c event-unixoid.c: In function `event_stream_unixoid_create_stream_pair': event-unixoid.c:287: warning: cast from pointer to integer of different size event-unixoid.c:288: warning: cast from pointer to integer of different size gcc -c -g -O2 -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -D_BSD -I/usr/dt/include process-unix.c process-unix.c: In function `connect_to_file_descriptor': process-unix.c:189: warning: cast to pointer from integer of different size process-unix.c: In function `unix_init_process_io_handles': process-unix.c:703: warning: cast from pointer to integer of different size process-unix.c: In function `unix_create_process': process-unix.c:777: warning: cast to pointer from integer of different size process-unix.c:777: warning: cast to pointer from integer of different size process-unix.c: In function `unix_open_network_stream': process-unix.c:1542: warning: cast to pointer from integer of different size process-unix.c:1543: warning: cast to pointer from integer of different size process-unix.c: In function `unix_open_multicast_group': process-unix.c:1703: warning: cast to pointer from integer of different size process-unix.c:1704: warning: cast to pointer from integer of different size gcc -c -g -O2 -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -D_BSD -I/usr/dt/include process.c process.c: In function `get_process_from_usid': process.c:215: warning: cast to pointer from integer of different size process.c: In function `init_process_io_handles': process.c:479: warning: cast to pointer from integer of different size process.c: In function `deactivate_process': process.c:1854: warning: cast to pointer from integer of different size The only other warnings with an -O2 build were: gcc -c -g -O2 -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -D_BSD -I/usr/dt/include sysdep.c sysdep.c: In function `child_setup_tty': sysdep.c:457: warning: large integer implicitly truncated to unsigned type sysdep.c:458: warning: large integer implicitly truncated to unsigned type sysdep.c:491: warning: large integer implicitly truncated to unsigned type sysdep.c: In function `tty_init_sys_modes_on_device': sysdep.c:1553: warning: large integer implicitly truncated to unsigned type sysdep.c:1554: warning: large integer implicitly truncated to unsigned type sysdep.c:1567: warning: large integer implicitly truncated to unsigned type sysdep.c:1573: warning: large integer implicitly truncated to unsigned type sysdep.c:1576: warning: large integer implicitly truncated to unsigned type sysdep.c:1579: warning: large integer implicitly truncated to unsigned type sysdep.c:1582: warning: large integer implicitly truncated to unsigned type sysdep.c:1585: warning: large integer implicitly truncated to unsigned type sysdep.c:1588: warning: large integer implicitly truncated to unsigned type sysdep.c:1594: warning: large integer implicitly truncated to unsigned type But I ended up with: Dumping under the name xemacs Purespace usage: 1045960 of 1045960 (100%). Impurities: conses used: 14385 conses free: 2264 cons storage: 272384 symbols used: 7586 symbols free: 4 symbol storage: 367792 vectors used: 595 vectors total length: 33059 vector storage: 278752 short strings used: 1448 long strings used: 1 strings free: 3368 short strings total length: 64603 short string storage: 90112 long strings total length: 57290 string header storage: 117856 floats used: 2 floats free: 22 float storage: 2048 markers used: 34 marker storage: 2016 extents used: 13 extent storage: 2032 symbol value lisp magics used: 24 symbol value lisp magic storage: 3264 symbol value varaliases used: 46 symbol value varalias storage: 2208 opaque lists used: 2 opaque list storage: 96 opaques used: 4 opaque storage: 196 color instances used: 1 color instance storage: 48 font instances used: 1 font instance storage: 64 range tables used: 1 range table storage: 32 faces used: 26 face storage: 3952 glyphs used: 18 glyph storage: 1440 specifiers used: 385 specifier storage: 47535 weak lists used: 385 weak list storage: 18480 char tables used: 12 char table storage: 25152 buffers used: 6 buffer storage: 3072 extent infos used: 4 extent info storage: 160 consoles used: 3 console storage: 576 command builders used: 1 command builder storage: 104 keymaps used: 122 keymap storage: 10736 devices used: 1 device storage: 280 frames used: 1 frame storage: 472 image instances used: 1 image instance storage: 128 windows used: 2 window storage: 1472 lcrecord lists used: 12 lcrecord list storage: 576 hashtables used: 263 hashtable storage: 21040 streams used: 2 streams on free list: 2 stream storage: 358 /bin/sh: 16111 Memory fault - core dumped make[2]: [xemacs] Error 139 (ignored) Testing for Lisp shadows ... /bin/sh: ./xemacs: cannot execute Which is about what I saw in b40. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634

1 participants
0 comments

Re: custom-file 26 years, 6 months

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Read my lips: I don't *want* to have a `.xemacs/' directory. Not > until this directory is absolutely necessary. For init and options, ok, this is worth discussing. But not even for putting your own packages, when you're not the sysadm, when you're not root on your machine, and when you didn't compile xemacs yourself ? > > 3. We have .xemacs anyway for the package system. > > I don't have it. Because you compile your own xemacs, which is not the case of the majority of people outside xemacs-beta. I tend to agree with Jan on this. Maybe we shouldn't use a .xemacs/init.el. We pretend emacs is a generic term, so let's stick to .emacs. But for custom, I'd really like a separate file, and there's one thing I hate, it's to add yet another .bullshit hidden file in my home dir. Just my opinion. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

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

Oscar Figueiredo

>>>>> "kkm" == Kirill M Katsnelson <kkm(a)kis.ru> writes: [...] kkm> [2 bark-PCM-8bit-8KBps-1ch.wav <audio/microsoft-wave>] According to ftp.isi.edu:/in-notes/iana/assignments/media-types/media-types, the official IANA list of assigned media types, `audio/microsoft-wave' is not a valid media type, you should use audio/x-wav instead (the x- prefix meaning it's an unofficial media type). Oscar

2 participants
1 comments

Re: 21.0 beta41, cygwin32, ~init-file-user doesn't work. 26 years, 6 months

Paul Stodghill

> I propose the following order of precedence: > Highest: Registry setting (when available). > 2. HOME > 3. HOMEDRIVE/HOMEPATH > > Kirill Sounds good to me.

1 participants
0 comments

Re: 21.0 beta41, cygwin32, ~init-file-user doesn't work. 26 years, 6 months

Rick Rankin

NT Emacs gets a number of values from the registry, e.g., initial font, geometry, etc. HOME could be included. I've seen code in XEmacs for reading the registry, so it seems that not all that much would have to be done. I'm not fond of the registry itself, but it's where Windows wants to store configuration settings. Right now, I'm using Kirill's "evilhack" method for setting initial font and geometry info. While this works, it's not very general. Or, has the registry already been discussed and dismissed? Rick -----Original Message----- From: Paul Stodghill <stodghil(a)CS.Cornell.EDU> To: Kirill M. Katsnelson <kkm(a)kis.ru> Cc: xemacs-beta(a)xemacs.org <xemacs-beta(a)xemacs.org>; xemacs-nt(a)xemacs.org <xemacs-nt(a)xemacs.org> Date: Tuesday, May 26, 1998 7:34 AM Subject: Re: 21.0 beta41, cygwin32, ~init-file-user doesn't work. >> Some time ago, Hrvoje Niksic wrote... >> |+ >> | Whatever we do, please note that (getenv "HOME") is definitely the >> | Wrong Thing to do. We should create a `user-home-directory' function >> | which would do the necessary magic of finding a system-specific home >> | directory. All the places that use (getenv "HOME") should be fixed to >> | use the new function. >> | >> | The suggestion comes from Ben. >> >> I think the better approach under Windows is to have a place for >> .emacs and stuff configurable. >> >> [ using a setup program to initialize XEmacs's notion of $HOME. ] >> >> Kirill > >This would be great for the binary distribution, but we still have to >figure out what needs to be done when compiling from source. > >And another thing, using (getenv "HOME") is probably the right thing to use >for `user-home-directory' under Cygwin32. BASH and TCSH both use >(getenv "HOME") to determine `~', so XEmacs should probably also... > >Thanks, guys. > >-- >Paul Stodghill <stodghil(a)cs.cornell.edu> >http://www.cs.cornell.edu/stodghil/ >

2 participants
1 comments

Re: custom-file 26 years, 6 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > I suggest not using an .xemacs-custom file but use > .xemacs/options.el Read my lips: I don't *want* to have a `.xemacs/' directory. Not until this directory is absolutely necessary. > 3. We have .xemacs anyway for the package system. I don't have it. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Speak softly and carry a +6 two-handed sword.

1 participants
0 comments

Re: [experimental PATCH] GC-Leak in tooltalk 26 years, 6 months

Hrvoje Niksic

Gunnar Evermann <Gunnar.Evermann(a)nats.informatik.uni-hamburg.de> writes: > --- src/tooltalk.c~ Fri May 1 03:11:07 1998 > +++ src/tooltalk.c Tue May 26 15:31:36 1998 > ＠＠ -1421,6 +1421,9 ＠＠ > Tooltalk_Message_plist_str = build_string ("Tooltalk Message plist"); > Tooltalk_Pattern_plist_str = build_string ("Tooltalk Pattern p plist"); > > + staticpro(&Tooltalk_Message_plist_str); > + staticpro(&Tooltalk_Pattern_plist_str); > + > #define MAKE_CONSTANT(name) do { \ > defsymbol (&Q_ ## name, #name); \ > Fset (Q_ ## name, make_int (name)); \ Looks good to me. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "A Real Programmer's code can awe with its fiendish brilliance, even as its crockishness appalls."

1 participants
0 comments

Re: 21.0 beta41, cygwin32, ~init-file-user doesn't work. 26 years, 6 months

David Bush

Darryl Okahata wrote: > "Kirill M. Katsnelson" <kkm(a)kis.ru> wrote: > > > `user-home-directory' should work in this case; maybe the name > > should be changed to `xemacs-private-files-directory' or something > > like that, not to be confused with real "home direcotry" concept. > > I'll add `user-home-directory' when I get around to submitting > my recent NT/$HOME changes to xemacs-patches (although I won't have the > time now to modify the various files to not use (getenv "HOME")). > Could you let me know as soon as you have something, perhaps even send an advanced copy? I am working on some related changes to fix similar issues in the Cygwin world and I feel this function would enhance the quality of my intended improvements. TIA david

1 participants
0 comments

Brief instructions for compiling XEmacs under Cygwin32 26 years, 6 months

Paul Stodghill

I have put very terse instructions for compiling XEmacs under Cygwin32 at http://www.cs.cornell.edu/stodghil/xemacs-cygwin32/xemacs-cygwin32.html This note includes, o URL's for where to obtain Cygwin32 and its patches, X11, etc. o Instructions and pointers for obtaining the XEmacs source. o Discussion of several of the problems that I encountered along the way. I assume that the reader is already familar with installing GNU'ish packages under UNIX. This note is meant to complement, not compete with, Hrvoje Niksic's `XEmacs on Windows FAQ'. Questions or comments to me. Thanks. -- Paul Stodghill <stodghil(a)cs.cornell.edu> http://www.cs.cornell.edu/stodghil/

1 participants
0 comments

[Success] 21.0 "San Clemente" XEmacs Lucid (beta41) on i386-pc-cygwin32 26 years, 6 months

Paul Stodghill

Before compiling, I o Changes CFLAGS to use -02 instead of -03. Below it says -03; that's wrong. o Applied two of Andy's patches. - <3.0.3.32.19980525091501.00a59280(a)exchange.parallax.co.uk> - <3.0.3.32.19980525094900.01031628(a)exchange.parallax.co.uk> > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /tmp/xemacs-20/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT MAPLE 4.0 19.2 i686 unknown ./configure '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' XEmacs 21.0-b41 "San Clemente" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /tmp/xemacs-20 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/cygwin32.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? default What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Additional header files: /usr/local/include Additional libraries: /usr/local/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. 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: --------------------------------------------------------- > /tmp/xemacs-20/beta.err does not exist!

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