August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

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

Jan Vroonhof

Ulrich Drepper <drepper(a)cygnus.com> writes: > I have bad news: even with Jan's patch to handle scrollbars somewhat > different I get a crash with Gnus in the same place. It seems, > though, that it crashes a bit less often. I ran this Emacs for 24 > hours and it was heavily used. I was afraid so. My patch makes the race condition less rare, but it doesn't make it go away. > If you have any more proposals how to instrument the code or patches > to try send them my way. This patch will (or should, because I didn't test it) make the crash go away while I ponder on how fix x_any_window_to_frame. If you get the message could please lookup the window id in the output of 'xwininfo -tree' Jan P.S. Greg, your lost selection bug could be related to this. Could you by any change find out the window id of the lost Selection message? Index: event-Xt.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/src/event-Xt.c,v retrieving revision 1.43 diff -u -u -r1.43 event-Xt.c --- event-Xt.c 1999/06/16 20:45:57 1.43 +++ event-Xt.c 1999/08/20 18:59:21 ＠＠ -777,9 +777,22 ＠＠ int bufsiz = sizeof (buffer); Status status; #ifdef XIM_XLIB - XIC xic = FRAME_X_XIC (x_any_window_to_frame - (get_device_from_display (event->display), - event->window)); + XIC xic; + struct frame *f; + + /* Maybe we should convert to a widget and then also try its parent + #### */ + f = x_any_window_to_frame (get_device_from_display (event->display), + event->window); + + if (f) + xic = FRAME_X_XIC (f); + else + { + xic = NULL; + fprintf (STDERR,"Failed to find frame for window %x\n", event->window); + } + #endif /* XIM_XLIB */ #endif /* HAVE_XIM */

1 participants
0 comments

udp for nt 25 years, 3 months

Stephen Tse

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: Please note that my patch is only for unix. I modified process-nt.c for compatibility only. I know nothing about winsock, anyone want to do udp for nt? > I am reporting a successful build on WinNT4sp4, VSC6.0, from CVS: > > cd d:\tmp\21.2\xemacs\ > cvs -z3 update -P -d -r release-21-2 > Compilation started at Fri Aug 20 10:08:57 1999 > > With following patch applied: > > > From: Stephen Tse <stephent(a)sfu.ca> > > Subject: udp support > > To: xemacs-patches(a)xemacs.org, eicq(a)aarg.net > > Date: 19 Aug 1999 17:44:25 -0700 > > Message-ID: <87672bjn6e.fsf(a)cr610941-a.rct1.bc.wave.home.com> > > It compiles and runs fine. > > Regards, > > Adrian

1 participants
0 comments

Re: kde-xemacs or gnome-xemacs? 25 years, 3 months

Jan Vroonhof

William Perry <wmperry(a)aventail.com> writes: > I think mostly-xt would be the easiest way to get it to work under XEmacs. > > The real downside is using C++ :) And the fact that your are never going to get RMS's permissions for that all important "as a special exception you are allowed to link with the QT 2.00, free edition". Unless they changed the licence yet again, QT 2.00 is Free, but not GPL compatible. Jan

2 participants
1 comments

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

Ulrich Drepper

Hi, I have bad news: even with Jan's patch to handle scrollbars somewhat different I get a crash with Gnus in the same place. It seems, though, that it crashes a bit less often. I ran this Emacs for 24 hours and it was heavily used. Anyhow, I still have the assert in and get Fatal error: assertion failed, file event-Xt.c, line 788, f != NULL The C backtrace is unusable as always #0 0x402bc601 in kill () #1 0x80af1a9 in fatal_error_signal (sig=6) at emacs.c:263 #2 <signal handler called> and as always I was going back to the group mode from looking at messages (i.e., the last character typed was a 'q'). If you have any more proposals how to instrument the code or patches to try send them my way. -- ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Cygnus Solutions `--' drepper at cygnus.com `------------------------

1 participants
0 comments

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

Karl Kleinpaste

Ulrich Drepper <drepper(a)cygnus.com> writes: > I've applied the patch Jan sent me and this seems to work. I had no > crash because of this problem. I want to observe that I applied this patch as well and have been running for 2 days with no more of this type of crash, when I had been getting them as often as twice a day previously. I wouldn't call it a definite fix just yet, but if it manages not to crash with these symptoms for another week, then the patch should be applied to the CVS tree.

1 participants
0 comments

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

Jan Vroonhof

Robert Pluim <rpluim(a)bigfoot.com> writes: > Here's a (possibly insane) suggestion: rather than dumping, why don't > we compile the lisp files to C? We could then make select portions > dynamically loadable, and remove all that unportable dumping code. This was Kyle's original plan. Olivier thinks it better to write the raw data directly to a file that you can mmap in (i.e. skip the compile stage). A middle road would be to write to an elf .so object directly so you can use the dynamic loader to get it back in. The first thing you need for this are pointers that are truly pointers, which is why minimal tag bits were invented. With the effects of also increasing the range of integers and (with the current naive allocator) a 50% memory overhead. Jan

6 participants
6 comments

gutter problems and building problems. 25 years, 3 months

Stef Epardaud

ok, i wanted to show you i had problems with gutters when it came to creating a second frame, but xemacs crashed without leaving me enough time. but i have several problems with the latest cvs 21.2 : i built it with ./configure --with-mule and when i run it it says: rock stephane 13:14 ~ > xemacs& [1] 12952 rock stephane 13:14 ~ > xemacs: Symbol `toggleClassRec' has different size in shared object, consider re-linking xemacs: Symbol `labelClassRec' has different size in shared object, consider re-linking --------- ok, that and the fact that when i try to launch a gnuclient with a file as argument, it just crashes and gives me: Fatal error (11). 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 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: # bind (frame-being-created) make-frame(nil #<x-device on "rock:11.0" 0x2b80>) # bind (device dest-frame new-frame old-device-num quick view flags list type) gnuserv-edit-files((x "rock:11.0") ((1 . "/tmp/mutt-rock-18306-2"))) eval((gnuserv-edit-files (quote (x "rock:11.0")) (quote (...)))) byte-code("..." [eval read-from-string gnuserv-string header] 4) # (condition-case ... . ((error (byte-code "ÀpÂ \"ÅrÆ ＠ A\"" ... 3)) (quit (byte-code "ÀpÂ \"ÅrÆÇÅ\"" ... 3)))) # bind (header string proc) gnuserv-process-filter(#<process "gnuserv" pid 18304 state:run> "5 (gnuserv-edit-files '(x \"rock:11.0\") '((1 . \"/tmp/mutt-rock-18306-2\")))c") # (condition-case ... . error) # bind (inhibit-quit) # (condition-case ... . error) # (catch top-level ...) [1] Segmentation fault xemacs ------------ you guys want a stack trace ? oh well, it does not seem to happen when i call gnuclient with no argument. ah, also i had a comment on the gutter: i load a file, then i load another file with C-x 5 f and the new frame has the gutter all painted with my background color and no text is visible on the gutter. first frame screenshot: http://tanglefoot.lunatech.com/~stephane/xemacs-gutter1.gif second one: http://tanglefoot.lunatech.com/~stephane/xemacs-gutter2.gif is it normal ? do you want more info? -- # Stef Epardaud, # There is no limit to the power of computing ... # Java Defeater # ... except men maybe ? # Earth # Lunatech Research, # Solar System # soon we will quit researching and start finding...

4 participants
9 comments

Re: kde-xemacs or gnome-xemacs? 25 years, 3 months

Bless Terje

>Unless they changed the licence yet again, QT 2.00 is Free, but not >GPL compatible. But GTK is GPL... :-) BTW, how the hell does this harmonize with the Windoze "native" port?

1 participants
0 comments

Re: gnuclient crash TOO OFTEN! 25 years, 3 months

Jan Vroonhof

Stef Epardaud <stef(a)lunatech.com> writes: > shame to me, xemacs is just crashing so often when i call gnuclient > that i even had to setenv EDITOR vi ! > i'm really saddened by this :( > is anybody else using gnuclient and havind problems ? No. > but my most important question is: how do i get something close to file > name or even line number in a lisp backtrace ? You don't. Normally it isn't necessary. Just to M-x find-function on a function call and you are taken to the definition (or M-. if you type "make tags"). > i'm still getting into C and all i saw from the C backtrace is that it > caught a sigsegv, so i wanted to look into the lisp backtrace, Well you can see it was making a new and trying to something with the X imput method. I don't think the lisp backtrace is very helpful here. > i am going to work on this problem even if it means taking years from me > to know all about C, because i hate having my whole xemacs session crash > when i want to send a mail. it is not acceptable for me. Well first of as the crash is in the xim-xlib code, you can just compile with --with-xim=no, however that doesn't solve the bug. The question is: what is so special about this gnuclient frame? XEmacs doesn't crash when you type C-x 5 2 does it? Or when you M-: (make-frame) RET? Are you by any chance starting XEmacs using -unmapped? If so, do you also get the gnuclient crash if you leave the "-unmapped" out? Jan

2 participants
1 comments

Re: A little thing that keeps me using emacs not xemacs sometimes 25 years, 3 months

Jan Vroonhof

Hans Reiser <reiser(a)idiom.com> writes: > meta-q does not join separate paragraphs. In emacs it interprets > as being a paragraph separator. I refer to whatever mode you get > into when you open fu.html using the sumo package set. Can you give a more specific example, for me if I type then I get aap noot mies vis vuur M-q both in GNU Emacs 20.3 (html-helper mode) and in XEmacs (psgm + psgml-html/html-helper-hack + hm--html-minor-mode). I presume what you want is aap noot mies vis vuur Jan

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