Re: Crash: XSetWMIconName, x_set_name_internal, prepare_menu_bars

[Kim F. Storm]

Chong Yidong <address@hidden> writes:

> Reiner Steib <address@hidden> writes:
>
>> report-emacs-bug wrote:
>>
>>> Please describe exactly what actions triggered the bug
>>> and the precise symptoms of the bug:
>>
>> My Emacs session which has been already running for several days
>> (notebook with suspend to disk) crashed.  I don't recall which command
>> triggered the bug.
>>
>> (gdb) bt 
>> #0  0xb74fc4ca in memcpy () from /lib/libc.so.6
>> #1  0xb77a049e in XChangeProperty () from /usr/lib/libX11.so.6
>> #2  0xb77c0711 in XSetTextProperty () from /usr/lib/libX11.so.6
>> #3  0xb77c0793 in XSetWMIconName () from /usr/lib/libX11.so.6
>> #4  0x080d550a in x_set_name_internal (f=0xa4dd960, name=222515027)
>>     at ~/.../cvs-HEAD/emacs/src/xfns.c:1653
>> #5  0x0807efec in prepare_menu_bars ()
>>     at ~/.../cvs-HEAD/emacs/src/xdisp.c:9015
>>
>> ...
>
> I'll dig around and see what I can find, but OTOH this looks like a
> crash in the X libraries, probably not related to Emacs.

I had a crash yesterday with the emacs 22 branch (not fully
up-to-date, but close):

 GNU Emacs 22.0.990.1 (i686-pc-linux-gnu, GTK+ Version 2.8.20) of 2007-05-23 on 
kfs-lx

It is built on an up-to-date Debian Stable system.

Emacs had probably been running for approx. 20 hours, and the last
command I executed which triggered the crash was C-x 5 b (that's
ido-switch-buffer-other-frame), selected a buffer from the list, and
hit RET.

I think it crashed while creating the new frame; I don't recall
seeing the frame appear, but I'm not absolutely sure.

The value of default-frame-alist is:

((vertical-scroll-bars . right)
 (left . 10)
 (top . 50)
 (font . "-Misc-Fixed-Medium-R-Normal--13-120-75-75-C-80-ISO8859-1")
 (wait-for-wm)
 (tool-bar-lines . 1)
 (menu-bar-lines . 1)
 (right-fringe)
 (left-fringe))

My window manager is KDE

Unfortunately, it happened while I was installing Debian on a new PC,
so I wasn't running under gdb at the time.

I've tried to reproduce the crash at least a 100 times, but haven't
been able to repeat it.

-- 
Kim F. Storm <address@hidden> http://www.cua.dk