April 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Crash in XEmacs 21.0 "20 minutes to Nikko" with gnuserv/gnuclient 25 years

obscurity

(This is the right place to send crash reports, right?) I've got an easily-reproduceable crash in XEmacs 21.0 "20 minutes to Nikko", when using gnuserv/gnuclient. If I start xemacs, run gnuserv-start, flip to another virtual console (this is on linux) run gnuclient, and then exit gnuclient (with or without doing any actual editing), then xemacs on the original virtual console barfs, with the following : |Fatal error: assertion failed, file event-Xt.c, line 1863, closure | |Fatal error (6). |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: | | kill-emacs() | # bind (arg) | save-buffers-kill-emacs(nil) | # bind (command-debug-status) | call-interactively(save-buffers-kill-emacs) | # (condition-case ... . error) | # (catch top-level ...) The output from where in gdb is : |#0 0x4024e811 in __kill () |#1 0x80aa381 in fatal_error_signal (sig=6) at emacs.c:262 |#2 <signal handler called> |#3 0x4024e811 in __kill () |#4 0x4024f84f in abort () at ../sysdeps/generic/abort.c:83 |#5 0x80ac5a7 in assert_failed (file=0x8204e49 "event-Xt.c", line=1863, | expr=0x8204fd8 "closure") at emacs.c:2608 |#6 0x818c960 in emacs_Xt_unselect_console (con=0x841df10) at event-Xt.c:1863 |#7 0x80dd0ec in event_stream_unselect_console (con=0x841df10) | at event-stream.c:621 |#8 0x809543a in delete_console_internal (con=0x841df10, force=1, | called_from_kill_emacs=1, from_io_error=0) at console.c:702 |#9 0x80abe6a in Fkill_emacs (arg=137431604) at emacs.c:2187 |#10 0x80b2889 in funcall_recording_as (recorded_as=137514592, nargs=0, | args=0xbffff76c) at eval.c:3197 |#11 0x80b2abd in Ffuncall (nargs=1, args=0xbffff76c) at eval.c:3238 |#12 0x808a9a2 in Fbyte_code (bytestr=136916060, vector=136916172, maxdepth=11) | at bytecode.c:416 |#13 0x80b39f2 in funcall_lambda (fun=136916552, nargs=1, arg_vector=0xbffff888) | at eval.c:3597 |#14 0x80b29d1 in funcall_recording_as (recorded_as=137514732, nargs=1, | args=0xbffff884) at eval.c:3214 |#15 0x80b2abd in Ffuncall (nargs=2, args=0xbffff884) at eval.c:3238 |#16 0x808da3e in Fcall_interactively (function=137514732, | record_flag=137431604, keys=137431604) at callint.c:949 |#17 0x80b1037 in Fcommand_execute (cmd=137514732, record=137431604, | keys=137431604) at eval.c:2584 |#18 0x80e45a6 in execute_command_event (command_builder=0x84f32e8, | event=139543904) at event-stream.c:4346 |#19 0x80e5317 in Fdispatch_event (event=138656524) at event-stream.c:4685 |#20 0x8092ed5 in Fcommand_loop_1 () at cmdloop.c:579 |#21 0x8092c65 in command_loop_1 (dummy=137431604) at cmdloop.c:494 |#22 0x80af8e1 in condition_case_1 (handlers=137431716, | bfun=0x8092c18 <command_loop_1>, barg=137431604, | hfun=0x8092104 <cmd_error>, harg=137431604) at eval.c:1653 |#23 0x80930a8 in command_loop_2 (dummy=137431604) at cmdloop.c:256 |#24 0x80af4cc in internal_catch (tag=137506004, | func=0x8093074 <command_loop_2>, arg=137431604, threw=0x0) at eval.c:1328 |#25 0x8092547 in initial_command_loop (load_me=137431604) at cmdloop.c:305 |#26 0x80ab605 in xemacs_21_0_b67_i686_pc_linux (argc=1, argv=0xbffffcc8, | envp=0xbffffcd0, restart=0) at emacs.c:1705 |#27 0x80abd09 in main (argc=1, argv=0xbffffcc8, envp=0xbffffcd0) | at emacs.c:2122 |(gdb) If anyone wants any more information, just let me know (I've got the corefile copied). -- obscurity. "Only the great masters of style ever succeed in being obscure." - Oscar Wilde

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?2 and 0) 25 years

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > O.K. Would it be acceptable to you to make `ebola' be a type of > error checking so you could disable it via configure? ie. > --error-checking=all-but-ebola? or something like that? I think it would be a bad idea to do this. Ebola is not error checking in the XEmacs sense of the word, since it doesn't cause core dumps.

3 participants
2 comments

Re: BUG REPORT: Custom Unwanted Face/Color interaction 25 years

Pete Ware

<mike.fabian(a)mail.rhein-ruhr.de> writes: > and get prompted for a password in the minibuffer. After entering the > password, ALL buffers in the current frame have a "midnightblue" > background, not only the *shell* buffer. Sounds like the code that does the reverse video during a keyboard grab is restoring the background for the default faces from the current buffers. --pete

1 participants
0 comments

Re: Patches to split the Options/Font menu based on the first char 25 years

Didier Verna

Tudor Hulubei writes: >> But still, a gtk port doesn't mean that we'll get rid of the other ports >> that we have already Tudor> Why not? Just to add another argument to what Glynn said, Motif for instance, is a toolkit that we support and that is shipped with some machines (like Suns. other ones?). So there are people who build xemacs with this toolkit because it's already there. Asking them to install another toolkit if they want a better support is okay, but IMHO _forcing_ them to do it is not. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Properties and readonly objects 25 years

Olivier Galibert

Should put and remprop be accepted on lisp-level readonly objects? I am not talking about objects readonly at C level (aka, pure objects). And before you tell me that we don't yet have objects readonly at lisp level only, be sure that I know that :-) OG.

1 participants
0 comments

Re: The patch to end all redisplay problems. 25 years

Jan Vroonhof

Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: > > Unfortunately, it probably isn't. On the serious side I think this bug > > is responsible for a lot of the glitches we have been seeing. > > cool, but there are still various problems with the start marker and > the line start cache. These trigger for example the assertion failure > Martin reported and maybe also Colin's. > > as a simple example try: > xemacs -nw -vanilla > (set-window-start (selected-window) 10) > C-l The window configuration stuff also messes with the window-start markers, so it won't surprise me if there are problems there too. set-window-configuration just blindly copies the old information without checking it is still valid. Jan

1 participants
0 comments

Re: Patches to split the Options/Font menu based on the first char 25 years, 1 month

Didier Verna

Tudor Hulubei writes: Tudor> I think the generic implementation belongs in the toolkit, and even if Tudor> it is present there, it should not be abused. True. Tudor> The purpose of my hack was to address the issue temporarily, for those Tudor> menus that do not address it already (Options/Font & (later) Tudor> Edit/TextProperties). All other menus do adress the problem in their Tudor> own way (the Buffers menu is an example). Not so. If you're talking about the way it splits buffers into categories, I don't call this a "way of adressing the problem". If you happen to have many buffers in the misc submenu for instance, you'll get the problem. >> From an UI perspective, it doesn't make much sense to put fonts in Tudor> menus anyway. It doesn't make much sense to have a menu with more than a dozen entries, or one or two sub menus in general. Tudor> To sum up, my idea was to make the Options/Font menu usable until a Tudor> Qt/GTK port will help get rid of it. But still, a gtk port doesn't mean that we'll get rid of the other ports that we have already, and not all of them have this feature. So I still think that it would be good to have this feature in Lisp. However, package authors shouldn't have to deal with it by hand, so something like an implicit filter would be nice. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

4 participants
3 comments

Re: 'quoted-insert broken?' 25 years, 1 month

Adrian Aichner

>>>>> "Matthew" == Matthew Persico <Matthew.Persico(a)lazard.com> writes: Matthew> Ok. Here it is. I started xemacs like this: Matthew> xemacs foo.c Matthew> where foo.c does not exist. I set the debug on error Matthew> option on and then entered this text in the foo.c buffer: Matthew> main() { Matthew> int i; Matthew> I then placed the cursor AFTER the semi-colon on line 2 Matthew> and attempted to put a tab in, as if to space a trailing Matthew> comment, and got this text in the *Backtrace* buffer: Matthew> Signaling: (wrong-type-argument integerp ?\t) Matthew> int-char(?\t) Matthew> read-quoted-char() Matthew> quoted-insert(1) Matthew> call-interactively(quoted-insert) Matthew, seemse like your 21.2-b13 no-mule has a different definition of `quoted-insert' than mine, 21.2-b13 mule, native Windows NT. Did you apply any patches, namely to simple.el? My definition of the function comes from d:\export\home\tmp\21.2\xemacs\lisp\simple.el and does not attempt to convert the `integer' ?\t (which it is not) into a character (which it already is). When I evaluate this: (int-char ?\t) I get that: Signaling: (wrong-type-argument integerp ?\t) int-char(?\t) eval((int-char ?\t)) eval-interactive((int-char ?\t)) eval-last-sexp(nil) call-interactively(eval-last-sexp) Try M-x find-function RET quoted-insert RET and see where it takes you. My suspision is that you get a bad definition of that function. Let's see whether I'm correct. Adrian Matthew> Do you need more? Matthew> -------- Original Message -------- Matthew> Subject: Re: 'quoted-insert' broken? Matthew> Date: 26 Mar 1999 23:42:29 +0100 Matthew> From: Adrian Aichner <aichner(a)ecf.teradyne.com> Matthew> To: xemacs-beta(a)xemacs.org Matthew> References: Matthew> <A69969F402E9B0228525674000774A6B.007770C280256740(a)notes.teradyne.com> >>>>> "Matthew" == Matthew Persico <Matthew.Persico(a)lazard.com> writes: Matthew> Running xemacs 21.2.13 on sloaris 2.6, no mule. Tried to Matthew> type keystrokes 'C-q tab' in cperl and c modes to get a Matthew> tab at the end of the line before a comment. I got this Matthew> error: Matthew> wrong type argument: integerp, ?\t Matthew> What other info/steps are required to help diagnose? Matthew> Try Matthew> Options -> General Options -> Debug On Error Matthew> run the offending operation and send the contents of Matthew> *Backtrace* to this list. Matthew> Regards, Matthew> Adrian Matthew> Matthew O. Persico Matthew> http://www.lazard.com Matthew> Opinions expressed are MINE, not Lazard's. Matthew> -- Matthew> Adrian Aichner Teradyne GmbH, European Design Center Matthew> Integra Test Division Telephone +49/89/41861(0)-208 Matthew> Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) Matthew> D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

2 participants
1 comments

Re: The patch to end all redisplay problems. 25 years, 1 month

Gunnar Evermann

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > :-) indeed :-) > Unfortunately, it probably isn't. On the serious side I think this bug > is responsible for a lot of the glitches we have been seeing. cool, but there are still various problems with the start marker and the line start cache. These trigger for example the assertion failure Martin reported and maybe also Colin's. as a simple example try: xemacs -nw -vanilla (set-window-start (selected-window) 10) C-l I'm working on this, but won't have much time next week... Gunnar -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

1 participants
0 comments

Re: change \C-m binding to newline-and-indent 25 years, 1 month

Dmitry Yaitskov

SL Baur <steve(a)xemacs.org> wrote: > Per Abrahamsen <abraham(a)dina.kvl.dk> writes in xemacs-beta(a)xemacs.org: > > > But even on other days, I'd prefer the default configuration of Emacs > > to be as CUA compliant as possible, and then some. > ... > > What does CUA stand for? Common User Interface. I am not sure who invented it, but IIRC MS Windows is (or is it 'are'?) supposed to follow it. Probably Motif too? > > > Having thus lost all credibility, I can comment on CR's proposal, > > which apparently isn't specific for this day. I believe it is a bad > > idea, even though it is what 99% of the users will want. I think > > programs should be stupid, until the user explicitly tells them to be > > smart. In a text editor, something as basic as the carriage return > > key should only insert a new line, not try to be smart. Not by > > default. Once the user has discovered what the `C' or `TeX' in the > > second line from the bottom means, he can start change the defaults. > > Maybe it should be easier to enable `smart return' though. > > I agree with not changing the default. I prefer C-j to get automatic > indentation. On the other hand, cc-mode has gotten so `smart' lately > that I tend to edit C code in fundamental-mode now. > > I think changing the [(control m)] binding sucks, but I don't intend > to fight against a strong consensus. I despise rebinding [(control c)], > [(control x)], and [(control v)] with a passion, however if someone > can make Kim Storm's code work with XEmacs, I am not opposed to making > it a default if it is installed (ie. by having it autoload initialization). Pardon a stupid question - what are, if any, the default XEmacs bindings for the "old" Windows-style cut and paste keys (Ctrl-Ins, Shift-Ins and Shift-Del)? If they are not used, they could IMHO be good candidates for cut and paste bindings, *if* we are talking about this at all... withtout losing such basic emacs keys as C-x etc. -- Cheers, -Dima.

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 April 1999