Re: gnuclient crash TOO OFTEN!
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