August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Solaris dump-time message 25 years, 3 months

SL Baur

Solaris people, what does this mean? Dumping under the name xemacs unexec(): dldump(/usr/local/devel/miho-optimized/src/xemacs): ld.so.1: ./temacs: fatal: /usr/local/devel/miho-optimized/src/xemacs: unknown dynamic entry: 1879048176 uname -a: SunOS miho 5.6 Generic_105181-05 sun4u sparc ../xemacs-21.2/configure '--with-mule' '--debug=no' '--error-checking=none' '--extra-verbose=no' '--site-prefixes=/usr/local' '--x-includes=/usr/local/X11R6/include' '--x-libraries=/usr/local/X11R6/lib' '--compiler=gcc' '--mail-locking=file' '--srcdir=../xemacs-21.2' '--cflags=-g -O3' '--with-xim=xlib' '--site-includes=/usr/lib/locale/ja/wnn/demo/include' '--site-libraries=/usr/lib/locale/ja/wnn/lib' '--with-widgets=athena3d' '--with-cde=no' '--with-tooltalk=no' '--with-scrollbars=athena3d' '--with-dialogs=athena3d' XEmacs 21.2-b19 "Shinjuku" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /usr/local/devel/xemacs-21.2 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -g -O3 Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/dt/include /usr/local/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/local/X11R6/lib Additional header files: /usr/lib/locale/ja/wnn/demo/include Additional libraries: /usr/lib/locale/ja/wnn/lib Additional prefixes: /usr/local Runtime library search path: /usr/lib/locale/ja/wnn/lib:/usr/local/lib:/usr/dt/lib:/usr/local/X11R6/lib:/usr/local/qt/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Compiling in support for Canna on Mule. Compiling in support for the WNN input method on Mule. Using WNN version 6. Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Athena-3d scrollbars. Using Athena-3d native widgets. Using Athena-3d dialog boxes. Compiling in DSO module support. movemail will use "dot-locking" for locking mail spool files.

1 participants
0 comments

Re: XEmacs has just (more than) doubled in size 25 years, 3 months

SL Baur

Marcus Thiessel <marcus(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > SL Baur writes: >> To clarify this, both of these binaries have identical configurations, >> they are both built with -g, I haven't changed any system software >> since I installed gcc-2.95 on August 4th. They have identical lists >> of shared libraries as shown by ldd. > Is that also true for XEmacs 21.2.x snapshots or just the latest? They are two snapshots. One from yesterday and one from three days ago. I'm doing a new build with the latest sources now. The only possibility left is that dumping is freshly broken on Solaris.

1 participants
0 comments

Re: Latest 21.2 fails under Solaris 2.5.1/X11R5 25 years, 3 months

Raymond Toy

>>>>> "Damon" == Damon Lipparelli <lipp(a)primus.com> writes: Damon> Starting with the earliest gutter changes, I haven't been able to either Damon> build or run XEmacs under Solaris 2.5.1 and X11R5. If I re-configure and Damon> build under Solaris 2.6 and X11R6, things are fine. Damon> Is X11R5 (or Solaris 2.5.1) outdated? Is anyone else seeing problems with Damon> this configuration? I don't have access to the latest CVS version of 21.2, but 21.2.19 builds and runs pretty well for me using Solaris 2.5.1 and Openwindows. Ray uname -a: SunOS edgedsp4 5.5.1 Generic_103640-24 sun4u sparc SUNW,Ultra-30 ./configure '--verbose' '--extra-verbose' '--with-mule' '--with-pop' '--package-path=/apps/public/XEmacs/lib' '--prefix=/apps/public/XEmacs/21.2' '--bindir=/apps/public/XEmacs/21.2/bin/solaris2.5.1' '--with-workshop' '--with-dialogs=motif' '--with-sound=both' '--site-includes=/apps/public/solaris2.5/usr/openwin/include /apps/public/solaris2.5/include' '--site-libraries=/apps/public/solaris2.5/usr/openwin/lib /apps/public/solaris2.5/lib' XEmacs 21.2-b19 "Shinjuku" configured for `sparc-sun-solaris2.5.1'. Where should the build process find the source code? /apps/public/XEmacs/src/xemacs-21.2.19 What installation prefix should install use? /apps/public/XEmacs/21.2 What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.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? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/dt/include /usr/openwin/include Where do we find X Windows libraries? /usr/dt/lib /usr/openwin/lib Additional header files: /apps/public/solaris2.5/usr/openwin/include /apps/public/solaris2.5/include Additional libraries: /apps/public/solaris2.5/usr/openwin/lib /apps/public/solaris2.5/lib Runtime library search path: /apps/public/solaris2.5/usr/openwin/lib:/apps/public/solaris2.5/lib:/usr/dt/lib:/usr/openwin/lib:/apps/gnu/solaris2.5/lib/gcc-lib/sparc-sun-solaris2.5.1/2.7.2.2:/apps/gnu/solaris2.5/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in both network and native sound support. Compiling in support for Berkeley DB. Compiling in support for DBM. Compiling in support for LDAP. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for ToolTalk. Compiling in support for Sun WorkShop. Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Motif native widgets. Using Motif dialog boxes. Compiling in DSO module support. movemail will use "dot-locking" for locking mail spool files. Using POP for mail access. Compiling in extra code for debugging. 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: ---------------------------------------------------------

1 participants
0 comments

Latest 21.2 fails under Solaris 2.5.1/X11R5 25 years, 3 months

Damon Lipparelli

Starting with the earliest gutter changes, I haven't been able to either build or run XEmacs under Solaris 2.5.1 and X11R5. If I re-configure and build under Solaris 2.6 and X11R6, things are fine. After the build completed, I ran "src/xemacs -q". An XEmacs window popped up, but disappeared quickly. The attached was spewed out in the xterm I ran in. Is X11R5 (or Solaris 2.5.1) outdated? Is anyone else seeing problems with this configuration? Thanks, -lipp <<X11R5-error.txt>> <<Installation>>

1 participants
0 comments

Re: [Jan Vroonhof <vroonhof@math.ethz.ch>] Re: constantly crashing in Gnus 25 years, 3 months

Ulrich Drepper

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > However I looked at it again, and I think that is wrong. The window is > a horizontal scrollbar!. Can you remember whether one of your windows > had a horizontal scrollbar just before you typed the keys? They definitely had. The summary has many lines as has the text of the message. > Ulrich could you try this patch? (sorry for using you as a guinea pig > like that instead of giving you a work around to get rid of the > crashes, but you seem to be the only one who can reproduce it failry > consistently). I'll give it a try. I have no problems with testing it since I don't loose data and it will hopefully help. -- ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Cygnus Solutions `--' drepper at cygnus.com `------------------------

1 participants
0 comments

XEmacs doing its own C backtraces 25 years, 3 months

Jan Vroonhof

> What you could do, perhaps, is to generate a C backtrace yourself in > the functions catching the signals. This will not be very portable > but I've added in glibc 2.1 a function to do just that. There is also > some code using this to generate backtraces in signal handlers. Nice idea, even if only works using glibc 2.1 Jan

1 participants
0 comments

Re: [Jan Vroonhof <vroonhof@math.ethz.ch>] Re: constantly crashing in Gnus 25 years, 3 months

Jan Vroonhof

> I do now. I had to correct the patch, tough. There is an obvious > type (a second definition of xic in the last line) and there is no > function x_any_window_or_parent_to_frame, so I use > x_any_window_to_frame. Is the former a 21.2 thing and should be > available in 21.1 as well? No. Ditch that patch completely. I should not write late night patches :-(. However I now have another better theory. > > It would be very nice to find out why the backtraces are cut short.. > > I have seen that before. I hope it doens't become widespread because > > debugging crashes will become close to impossible that way. > > Yeah, I know. But I really cannot say what the problem is. Somehow > the backtrace mechnism interacts badly with the stack frame generated > by the libc/kernel. Aparrently you can get the right backtrace if you use run Xemacs directly under gdb. Karl Kleinpaste did that and based on his info we think it is a problem with x_any_window_to_frame. [Late breaking news: That you hit the assert is another confirmation of that]. More importantly Karl was able to find out the offending window id and a window-tree dump of the frame (see the archive). The conclusion was made that the menu window was involved. However I looked at it again, and I think that is wrong. The window is a horizontal scrollbar!. Can you remember whether one of your windows had a horizontal scrollbar just before you typed the keys? I also think I know what the problem is x_any_window_to_frame checks whether this window is a scrollbar using x_window_is_scrollbar. That essentially consists of if (f->mirror_dirty) update_frame_window_mirror (f); return (EMACS_INT) x_scrollbar_loop (X_WINDOW_IS_SCROLLBAR, f->root_window, f->root_mirror, 0, win); The "x_scrollbar_loop" basically recurses through the XEmacs window structure to find a window whois scrollbar window has window id 'win'. The problem is with update_frame_window_mirror(), this basically syncs the window and scrollbar structure with how it should be. However this is wrong! x_any_window_to_frame is called when we have an event generated for a particular window. This implies that the Xt-window belongs to a widget that is actually being displayed, i.e. to the old window structure. Ulrich could you try this patch? (sorry for using you as a guinea pig like that instead of giving you a work around to get rid of the crashes, but you seem to be the only one who can reproduce it failry consistently). (this is again untested. But I am fairly certain this will compile) My only worry is that update_frame_window_mirror could also be called by other functions in between. Index: scrollbar-x.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/src/scrollbar-x.c,v retrieving revision 1.14 diff -u -u -r1.14 scrollbar-x.c --- scrollbar-x.c 1998/06/02 03:50:57 1.14 +++ scrollbar-x.c 1999/08/18 17:49:35 ＠＠ -681,8 +681,11 ＠＠ if (!FRAME_X_P (f)) return 0; + /* No stupid! We do not want to do this. We are using this to process + events. These are generated by the _old_ structure. if (f->mirror_dirty) update_frame_window_mirror (f); + */ return (EMACS_INT) x_scrollbar_loop (X_WINDOW_IS_SCROLLBAR, f->root_window, f->root_mirror, 0, win); }

1 participants
0 comments

Re: XEmacs has just (more than) doubled in size 25 years, 3 months

SL Baur

SL Baur <steve(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > Same configuration options, current CVS for the monster. > -rwxrwxrwx 1 steve 23688 18546704 Aug 18 14:51 src/xemacs > -rwxrwxrwx 1 steve 23688 8690616 Aug 16 15:01 src/xemacs.RUNNING > This is bad. Any clues? To clarify this, both of these binaries have identical configurations, they are both built with -g, I haven't changed any system software since I installed gcc-2.95 on August 4th. They have identical lists of shared libraries as shown by ldd. Comparative output from size is: $ size src/xemacs* text data bss dec hex filename 2384350 3030336 0 5414686 529f1e src/xemacs 2063120 3035984 0 5099104 4dce60 src/xemacs.RUNNING Comparative sizes of the symbol tables: $ nm src/xemacs | wc 10473 30872 297690 $ nm src/xemacs.RUNNING | wc 10601 31263 304660 The larger binary has a *smaller* symbol table.

4 participants
3 comments

Re: xemacs source code HOWTO ? 25 years, 3 months

Jan Vroonhof

Stef Epardaud <stef(a)lunatech.com> writes: > while, and Java brainwashed me quite well, i got very confused as to all > the precompiler macros Don't worry. The preprocessor macro's scare everybody. They are way over the top, IMVHO. Try reading the "Internals" info file. Especially the GCPRO section (basically GCPRO is where the C part says to the lisp-engine: "I'm using this variable!"). After that simply read some code and ask _lots_ of questions. I would suggest you stay away from the redisplay code in the beginning. > i mean, i could not find a place where i could learn how all this fit > together, how i should declare new lisp structures, how and when to use > GC related functions, and how to organize the code i would add. Try reading the examples from the "modules" directory. They are fairly small and self-contained. Personally I think a good way too learn is to do real work :-). Try looking at the bug tracking system http:///cvs.xemacs.org/XEmacs-bugs for a few bugs you can reproduce and then try to work on that. Jan P.S. Here is a real bug if you want to learn about specifiers: When you use (set-specifier minimum-line-ascent 30 (current-buffer)) then the result of (window-height) does not change, but it should.

2 participants
2 comments

XEmacs has just (more than) doubled in size 25 years, 3 months

SL Baur

Same configuration options, current CVS for the monster. -rwxrwxrwx 1 steve 23688 18546704 Aug 18 14:51 src/xemacs -rwxrwxrwx 1 steve 23688 8690616 Aug 16 15:01 src/xemacs.RUNNING This is bad. Any clues?

2 participants
1 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 August 1999