* Emacs crash in X
@ 2003-01-03 19:44 Satyaki Das
0 siblings, 0 replies; only message in thread
From: Satyaki Das @ 2003-01-03 19:44 UTC (permalink / raw)
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.
Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.
In GNU Emacs 21.2.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2002-08-28 on astest
configured using `configure --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --with-gcc --with-pop --with-sound'
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_US
locale-coding-system: iso-latin-1
default-enable-multibyte-characters: t
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
I started emacs in gdb as follows:
$ gdb /usr/bin/emacs
(gdb) run -q --no-site-file
Then I created a second frame with: C-x 5 2
I move the new frame to a different workspace (it is important
to move it to a different workspace as moving it to a
different viewport in window managers that support both
doesn't cause the crash). At this point I have two frames both
displaying the *scratch* buffer.
In the new frame I load ~/pp.el with: C-x C-f ~/pp.el RET
Contents of ~/pp.el:
-- start of pp.el --
(progn
(setq focus-follows-mouse nil)
(select-frame-set-input-focus
(window-frame (get-buffer-window "*scratch*" t))))
-- end of pp.el --
Now I move to the end of pp.el and evaluate the lisp
expression with: M-> C-x C-e
This causes Emacs to die. In gdb from where emacs was started
I see the following output:
X protocol error: BadMatch (invalid parameter attributes) on protocol request 42
Program exited with code 0106.
I use the metacity window manager. I have been able to
reproduce the exact same crash with CVS version of emacs that
I checked out on 2002-12-25. That version reports its version
as 21.3.50.3.
I came across this problem while using ILISP which is an
interface to various implementations of Common Lisp. I
minimized the code that needed to be run to crash emacs.
Hope this helps,
Satyaki
Recent input:
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <down> <down> <down> <down> <down> <down> <down>
<down> <up> <up> <up> <up> C-x k <return> M-x <up>
<up> <return>
Recent messages:
call-interactively: End of buffer [2 times]
Wrote /home/satyaki/pp.el
Undo!
call-interactively: Quit
Making completion list... [2 times]
byte-code: Quit
Loading info...done
Composing main Info directory...
Mark set
Composing main Info directory...done
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-01-03 19:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-01-03 19:44 Emacs crash in X Satyaki Das
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).