January 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Solaris and gcc 2.95.2? 23 years, 3 months

Raymond Toy

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> At 12:04 11/01/01 -0500, Raymond Toy wrote: >> X11R6.4 and openwin? Andy> I am totally convince that not using these would make many of your problems go away :) Well, a lot of my problems would go away if I stopped using computers all together, but then I'd need to find a new job as well. :-) However, my problems still exist if I build and link with just openwin, which is what I've been doing for a very long time. Just these last two build have I tried using X11R6.4. (Because GNOME doesn't work with the libICE we have, and I'm too lazy to get the IT guys to upgrade to the correct libICE because then everyone who wants GNOME will have to do it. It was far easier to use X11R6.4.) Ray

1 participants
0 comments

sunplay.c and sigcontext for solaris? 23 years, 3 months

Raymond Toy

At the end of sunplay.c there's the comment: /* #### sigcontext doesn't exist in Solaris. This should be updated to be correct for Solaris. */ static SIGTYPE sighandler (int sig) { The sigcontext for Solaris is actually called ucontext (in ucontext.h). And signal handlers are passed something like: handler(int signal, siginfo_t *code, struct ucontext *context) What is supposed to happen in sunplay with the sigcontext? Should all of these parameters in sighandler get passed on to sighup_handler and sigint_handler? Ray

1 participants
0 comments

Re: Crash in png_warning_func() 23 years, 3 months

Gunnar Evermann

Hi Kilian, foth(a)informatik.uni-hamburg.de (Kilian A. Foth) writes: > In XEmacs 21.2 (beta38) "Peisino,Ak(B" [Lucid] > (sparc-sun-solaris2.8, Mule) > Core was generated by `xemacs-21.2-b38 --vanilla'. > Program terminated with signal 11, Segmentation Fault. > #0 0x7f41a034 in _libc_kill () from /usr/lib/libc.so.1 > #1 0x911e0 in fatal_error_signal (sig=11) at emacs.c:535 > #2 <signal handler called> > #3 0x7f3b2158 in longjmp () from /usr/lib/libc.so.1 > #4 0x152084 in png_warning_func (png_ptr=0x772400, > msg=0x7f961cd8 "Application must be recompiled; version 1.0.6 was incompatible") > at glyphs-eimage.c:812 > #5 0x7f95e868 in png_error () from /opt/lib//libpng.so.2 > #6 <signal handler called> which version of libpng is that? (don't tell me that it is still the one I compiled three years ago :-)). Are you sure you are using the correct version of the headers when compiling xemacs? Gunnar

1 participants
0 comments

Re: [lauri@mail.eng.it (Gian Uberto Lauri)] URL [was: html-helper-mode updated] 23 years, 3 months

Adrian Aichner

>>>>> "Jerry" == Jerry James <james(a)eecs.ukans.edu> writes: Jerry> On the other hand, my ViaVoice module is *this* close to Jerry> completion (including the complete ViaVoice API, but in Jerry> Lispified form). :-) Sounds exciting! Jerry> -- Jerry> Jerry James -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

1 participants
0 comments

[lauri@mail.eng.it (Gian Uberto Lauri)] URL [was: html-helper-mode updated] 23 years, 3 months

Adrian Aichner

Hi All! Does anyone know what the status of this mode is WRT XEmacs? Any users here who recommend adding it as a separate package or make it part of some other package? Best regards, Adrian -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

3 participants
2 comments

Re: 21.2.39 hangs sometimes 23 years, 3 months

Raymond Toy

>>>>> "Valdis" == Valdis Kletnieks <Valdis.Kletnieks(a)vt.edu> writes: Valdis> On Wed, 10 Jan 2001 18:54:57 GMT, Andy Piper <andy(a)xemacs.org> said: >> We have a few of these reports. I have no idea what is causing them. Any X >> experts have any idea? Valdis> I have no idea offhand, but I've seen this under AIX 4.3.3 so it's probably Valdis> not a system or compiler issue. >> >0 0xfeb1437c in _poll () from /usr/lib/libc.so.1 >> >#1 0xfeace3e4 in select () from /usr/lib/libc.so.1 >> >#2 0xfeddd298 in _XWaitForReadable () from /usr/openwin/lib/libX11.so.4 >> >#3 0xfeda3514 in _XRead () from /usr/openwin/lib/libX11.so.4 >> >#4 0xfeda57dc in _XReply () from /usr/openwin/lib/libX11.so.4 >> >#5 0xfedab74c in XAllocColor () from /usr/openwin/lib/libX11.so.4 >> >#6 0x230d80 in allocate_nearest_color (display=0x68d000, colormap=52, >> >visual=0x69c700, color_def=0xffbedb68) at objects-x.c:65 >> >#7 0x2378e8 in x_generate_shadow_pixels (f=0x68d000, >> >top_shadow=0xffbedc24, bottom_shadow=0xffbedc20, background=13026763, >> >core_background=13026763) at redisplay-x.c:1632 Valdis> Out of curiosity, does anybody know what visual/depth Raymond Toy was Valdis> running at? I'm suspecting some sort of screw-up relating to a full colormap, Valdis> which "should only happen" on an 8-bit display, or if you've been blessed with Valdis> one of IBM's GXT255 cards, which does 24-bit with a subtly brokked colormap. I've set up my server for a default visual of 24-bit true-color, but the Sun X server has many, many visuals available. I used to use whatever default the server decided on but gv and ghostscript always ended up picking the first visual which was 8-bit. Ick. I now explicitly tell the server to use a 24-bit visual for gv and gs's benefit. One a good note, I haven't seen this happen since my original report, but I've upgraded to b40 and GNOME in the meantime. Ray

1 participants
0 comments

21.2.39 hangs sometimes 23 years, 3 months

Raymond Toy

This has happened a couple of times to me on 21.2.39 on Solaris 2.7, built using gcc 2.7.2.2. I don't know what causes it, but it just hangs. Very little CPU usage. For what it's worth, here's a backtrace from the offending program. Ray 0 0xfeb1437c in _poll () from /usr/lib/libc.so.1 #1 0xfeace3e4 in select () from /usr/lib/libc.so.1 #2 0xfeddd298 in _XWaitForReadable () from /usr/openwin/lib/libX11.so.4 #3 0xfeda3514 in _XRead () from /usr/openwin/lib/libX11.so.4 #4 0xfeda57dc in _XReply () from /usr/openwin/lib/libX11.so.4 #5 0xfedab74c in XAllocColor () from /usr/openwin/lib/libX11.so.4 #6 0x230d80 in allocate_nearest_color (display=0x68d000, colormap=52, visual=0x69c700, color_def=0xffbedb68) at objects-x.c:65 #7 0x2378e8 in x_generate_shadow_pixels (f=0x68d000, top_shadow=0xffbedc24, bottom_shadow=0xffbedc20, background=13026763, core_background=13026763) at redisplay-x.c:1632 #8 0x234c6c in x_bevel_area (w=0xd15000, findex=1, x=4, y=284, width=576, height=17, shadow_thickness=2, edges=15, style=EDGE_BEVEL_OUT) at redisplay-x.c:551 #9 0x1d9134 in bevel_modeline (w=0xd15000, dl=0x11) at redisplay-output.c:2372 #10 0x234a60 in x_output_display_block (w=0xd15000, dl=0x1586000, block=142, start=1, end=82, start_pixpos=4, cursor_start=0, cursor_width=0, cursor_height=0) at redisplay-x.c:509 #11 0x1d5220 in redisplay_output_display_block (w=0xd15000, dl=0x1586000, block=0, start=0, end=82, start_pixpos=4, cursor_start=0, cursor_width=0, cursor_height=0) at redisplay-output.c:1153 #12 0x1d2fd8 in compare_display_blocks (w=0xd15000, cdl=0x1595000, ddl=0x1586000, c_block=82, d_block=0, start_pixpos=4, cursor_start=0, cursor_width=0, cursor_height=0) at redisplay-output.c:520 #13 0x1d39ec in output_display_line (w=0xd15000, cdla=0xaa76a0, ddla=0xaa7420, line=0, force_start=4, force_end=580) at redisplay-output.c:643 #14 0x1d8ad4 in redisplay_output_window (w=0xd15000) at redisplay-output.c:2289 #15 0x1c7bf8 in redisplay_window (window=13717504, skip_selected=91) at redisplay.c:6169 #16 0x1c7e90 in redisplay_windows (window=13717504, skip_selected=1) at redisplay.c:6225 #17 0x1c70cc in redisplay_window (window=13312000, skip_selected=1) at redisplay.c:5855 #18 0x1c82cc in redisplay_frame (f=0x3d4a00, preemption_check=13312000) at redisplay.c:6225 #19 0x1c8554 in redisplay_device (d=0x69cb00, automatic=4016640) at redisplay.c:6467 #20 0x1c8a84 in redisplay_without_hooks () at redisplay.c:6556 #21 0x1c8d08 in redisplay () at redisplay.c:6613 #22 0x112758 in Fnext_event (event=12983320, prompt=3356676) at event-stream.c:2176 #23 0x8d9b8 in Fcommand_loop_1 () at cmdloop.c:574 #24 0x8d764 in command_loop_1 (dummy=6929664) at cmdloop.c:494 #25 0xb1ae8 in condition_case_1 (handlers=3356772, bfun=0x8d718 <command_loop_1>, barg=3356676, hfun=0x8dbac <cmd_error>, harg=3356676) at eval.c:1651 #26 0x8dcbc in command_loop_2 (dummy=3356676) at cmdloop.c:256 #27 0xb1658 in internal_catch (tag=3441100, func=0x8dc70 <command_loop_2>, arg=3356676, threw=0x0) at eval.c:1317 #28 0x8d060 in initial_command_loop (load_me=580720) at cmdloop.c:305 #29 0xad024 in xemacs_21_2_b39_sparc_sun_solaris2_7 (argc=1, argv=0xffbeead4, envp=0xffbeeadc, restart=0) at emacs.c:2253 #30 0xad848 in main (argc=1, argv=0xffbeead4, envp=0xffbeeadc) at emacs.c:2682

3 participants
2 comments

22.0: Yammer, screech, yowl ... 23 years, 3 months

Stephen J. Turnbull

... and the cat is out of the bag. The announcement is posted on c.emacs, c.e.xemacs, and xemacs-announce. The release plan is now linked from the XEmacs home page. We now return you to your regularly scheduled bug-hunt and feature-fest. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

1 participants
0 comments

Crash in png_warning_func() 23 years, 3 months

Kilian A. Foth

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.2 (beta38) "Peisino,Ak(B" [Lucid] (sparc-sun-solaris2.8, Mule) of Fri Dec 29 2000 on nats21 configured using `configure --with-mule --with-xpm --with-site-lisp=yes --package-path=/opt/lib/xemacs-21.2-b38/' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: M-x customize-face [Enter] default [Enter] causes the editor to crash. Lisp backtrace follows: # (unwind-protect ...) # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque-ptr, adr=0x2d997c) 0x346000> ...) # (unwind-protect ...) # bind (inhibit-quit) # (condition-case ... . error) # (catch top-level ...) Here is the beginning of the C backtrace: Core was generated by `xemacs-21.2-b38 --vanilla'. Program terminated with signal 11, Segmentation Fault. #0 0x7f41a034 in _libc_kill () from /usr/lib/libc.so.1 #1 0x911e0 in fatal_error_signal (sig=11) at emacs.c:535 #2 <signal handler called> #3 0x7f3b2158 in longjmp () from /usr/lib/libc.so.1 #4 0x152084 in png_warning_func (png_ptr=0x772400, msg=0x7f961cd8 "Application must be recompiled; version 1.0.6 was incompatible") at glyphs-eimage.c:812 #5 0x7f95e868 in png_error () from /opt/lib//libpng.so.2 #6 <signal handler called> #7 0x7f3b2158 in longjmp () from /usr/lib/libc.so.1 #8 0x152084 in png_warning_func (png_ptr=0x772400, msg=0x7f961cd8 "Application must be recompiled; version 1.0.6 was incompatible") at glyphs-eimage.c:812 #9 0x7f95e868 in png_error () from /opt/lib//libpng.so.2 #10 <signal handler called> #11 0x7f3b2158 in longjmp () from /usr/lib/libc.so.1 #12 0x152084 in png_warning_func (png_ptr=0x772400, msg=0x7f961cd8 "Application must be recompiled; version 1.0.6 was incompatible") at glyphs-eimage.c:812 #13 0x7f95e868 in png_error () from /opt/lib//libpng.so.2 (These four frames repeat, apparently indefinitely.)

1 participants
0 comments

XEmacs 22.0 Release Target and Call For Testers 23 years, 3 months

Stephen J. Turnbull

The following message is a courtesy copy of an article that has been posted to comp.emacs.xemacs,comp.emacs as well. Followup set to comp.emacs.xemacs, but the xemacs-beta mailing list is the preferred channel for discussion. The XEmacs Review Board has approved a proposal to integrate the features in the current development branch, and release the next version of XEmacs on March 1, 2001. Although XEmacs development code is always publically available, we hope that many users of the stable version and other versions of Emacs will take this chance to become beta testers. The version number will be 22.0.0, based on the proposed inclusion of several major new features. These are: o Integration of GTK XEmacs with the main line. o Availability of "native" widgets such as push buttons, progress bars, and tab controls, for constructing user interfaces in Emacs buffers. These are implemented as a generalization of buffer glyphs (such as ordinary text and images), and so have a familiar Lisp API. They will be more or less integrated with the GTK widgets in XEmacsen configured --with-gtk. o Integration of the Mule API for Emacs with the native Windows internationalization APIs on the Win32 platforms. Many other improvements and new features are also in the development tree. For more details, visit: http://www.xemacs.org/Releases/Public-21.2/ Discussion of the development process, bugs, etc will take place on the XEmacs Beta Testers mailing list xemacs-beta. (Occasional short progress reports will be posted to the comp.emacs.xemacs newsgroup.) To subscribe to xemacs-beta (or any XEmacs-related mailing list), visit http://www.xemacs.org/Lists/ or send an e-mail message to xemacs-beta-request(a)xemacs.org with `subscribe' (without the quotes) as the _body_ of the message. The prerelease tester versions will be available, as all XEmacs stable and development code is, by anonymous CVS and anonymous FTP. For procedures to access anonymous CVS and FTP, please visit http://cvs.xemacs.org/ ftp://ftp.xemacs.org/xemacs/beta/xemacs-21.2/ respectively. Prelease tarballs will be named something like xemacs-21.2.40.tar.gz (which is current). The code released on March 1 will initially be labelled "gamma." This indicates that it is as stable as we can make it through beta testing, and we have a high degree of confidence that no bugs that potentially cause data loss (including crashes and security holes) remain. The release will be promoted to "stable" upon acceptance by the XEmacs Stable Release Maintainer. During the "gamma" period the 21.1 series will continue to be maintained as the "stable version." It is recommended for environments where bugs, including configuration glitches and inadvertant backwards incompatibility, must be kept to the absolute minimum. The "gamma" version is intended to be suitable for inclusion in prerelease packages in downstream distributions (such as the Debian GNU/Linux "unstable" and "testing" distributions, or the Red Hat "Rawhide" distribution). It should also be appropriate for "power" users who are willing to trade the probability of some minor bugs for the most recent features. 11 January 2001 XEmacs 22.0 Release Manager Stephen J. Turnbull <stephen(a)xemacs.org> -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

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 January 2001