fvwm repeatedly crashing

Configuration Information [Automatically generated, do not change]:
uname: Linux jdiamond-nb2 4.1.2 #1 SMP PREEMPT Fri Jul 17 18:16:03 ADT 2015 x86_64 Intel® Core™ i7 CPU M 620 @ 2.67GHz GenuineIntel GNU/Linux
compiler flags: gcc -Wall -Wno-implicit-int -O2 -fPIC

FVWM Version: 2.6.5
FVWM_MODULEDIR: /usr/libexec/fvwm/2.6.5
FVWM_DATADIR: /usr/share/fvwm
FVWM_USERDIR: /home/zsd/.fvwm

Description:
fvwm occasionally crashes (a few times a day).

Repeat-By:
Since I’ve started trying to take note of when it crashes,
every time it was when I was switching tabs in firefox,
opening a new tab or closing a tab (I’m currently running ffx
38.6.0esr but this crashing problem has been occurring on and
off for quite a while, so it is not specific to that
particular version of ffx). However, I’m not certain that
changing tabs in firefox is the only time it happens.

Notes: here is some of the basic information as reported by gdb

% gdb =fvwm2 ~/core
GNU gdb (GDB) 7.6.1
Copyright © 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
This GDB was configured as “x86_64-slackware-linux”.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/
Reading symbols from /usr/bin/fvwm…done.

warning: core file may not match specified executable file.
[New LWP 26140]

warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need “set solib-search-path” or “set sysroot”?
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/lib64/libthread_db.so.1”.

warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff4afcd000
Core was generated by `/usr/bin/fvwm2’.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f23e2250dbc in free () from /lib64/libc.so.6
Traceback (most recent call last):
File “/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3600.4-gdb.py”, line 9, in
from gobject import register
File “/usr/share/glib-2.0/gdb/gobject.py”, line 3, in
import gdb.backtrace
ImportError: No module named backtrace
(gdb) where
#0 0x00007f23e2250dbc in free () from /lib64/libc.so.6
#1 0x00007f23e43a67a6 in XFreeStringList () from /usr/lib64/libX11.so.6
#2 0x0000000000485deb in FlocaleFreeNameProperty (ptext=ptext@entry=0x25e9710)
at Flocale.c:2358
#3 0x00000000004420ff in free_window_names (fw=fw@entry=0x25e9700,
nukename=nukename@entry=0, nukeicon=nukeicon@entry=1) at add_window.c:3171
#4 0x000000000047ffbb in EWMH_WMIconName (fw=0x25e9700,
ev=0x6d1780 <fev_event>, style=, any=)
at ewmh_names.c:175
#5 0x000000000042f110 in HandlePropertyNotify (ea=0x7fff4af29330)
at events.c:3628
#6 0x000000000042d874 in dispatch_event (e=e@entry=0x7fff4af293c0)
at events.c:4135
#7 0x000000000042e120 in HandleEvents () at events.c:4179
#8 0x000000000040b315 in main (argc=, argv=)
at fvwm.c:2591
(gdb) up
#1 0x00007f23e43a67a6 in XFreeStringList () from /usr/lib64/libX11.so.6
(gdb) up
#2 0x0000000000485deb in FlocaleFreeNameProperty (ptext=ptext@entry=0x25e9710)
at Flocale.c:2358
2358 Flocale.c: No such file or directory.
(gdb) up
#3 0x00000000004420ff in free_window_names (fw=fw@entry=0x25e9700,
nukename=nukename@entry=0, nukeicon=nukeicon@entry=1) at add_window.c:3171
3171 add_window.c: No such file or directory.
(gdb) up
#4 0x000000000047ffbb in EWMH_WMIconName (fw=0x25e9700,
ev=0x6d1780 <fev_event>, style=, any=)
at ewmh_names.c:175
175 ewmh_names.c: No such file or directory.
(gdb) up
#5 0x000000000042f110 in HandlePropertyNotify (ea=0x7fff4af29330)
at events.c:3628
3628 events.c: No such file or directory.
(gdb) up
#6 0x000000000042d874 in dispatch_event (e=e@entry=0x7fff4af293c0)
at events.c:4135
4135 in events.c
(gdb) up
#7 0x000000000042e120 in HandleEvents () at events.c:4179
4179 in events.c
(gdb) up
#8 0x000000000040b315 in main (argc=, argv=)
at fvwm.c:2591
2591 fvwm.c: No such file or directory.
(gdb) quit

FWIW:
(1) I’m using Slackware64-14.1 on a Fujitsu T900 with a Core i7
M620, 8 GB of ram.
(2) I’ve let memtest86 churn away for a long time with no reported
problems. No other program on my system is showing any problems,
so while I’m not certain that it isn’t a bad hardware problem, I
don’t see any evidence of that either.

I saved a couple of core dumps. If further information from those
would be of use let me know.

Any ideas? Thanks.

Hi,

please post your report on the FVWM workers mailinglist because it’s too specific for the forums. How to do this see here.

Thanks,

– Thomas –

Thanks. But…

I actually tried that first, and while I never got a bounce to my e-mail message, my message doesn’t show up when I visit the archives to which that page links:
mail-archive.com/fvwm-worker … llist.html
Further, when I get that web page to sort by date, the most recent date it lists for me is
2015/06/18 Re: Fvwm commit problem …
so I was beginning to think the mailing list was defunct.

At the risk of adding to the topic here, is that archive current? I guess I can send e-mail to the list owner, which I will do now.

[quote=“bobl33”]
Thanks. But…

I actually tried that first, and while I never got a bounce to my e-mail message, my message doesn’t show up when I visit the archives to which that page links:
fvwm-workers-request@fvwm.org?
Also it is important that you’ve send it as a pure text email - no html header shall included anywhere in the mail. For example my German provider web.de do this, whether I’ve set it to text :confused: Therefore I have to use a client for my web.de account or another provider which send true text emails (e.g. Google).
And last but not least only those email address from where you’ve sent the subscribe mail is valid after you’ve got an activasion email.

No it is working but …

… the update cycle is longer than on other mailinglists, I’m afraid :frowning:

[quote=“TF”]

Not until a minute ago. fvwm.org/contact/ doesn’t mention that you must be a member of fvwm-workers to e-mail to it, nor does the man page for fvwm-bug, so thanks for mentioning that.

I’ll try e-mailing the bug report (in plain text!) in a few minutes. I’m not sure whether I should expect a “you’re in” response to the subscribe request, but if nothing shows up in a while I’ll cross my fingers and e-mail the report.

https://quantumitinnovation.com/mobile-app-development-company-south-africa
An android is one of the widely used platforms in South Africa & developing an app for this platform is quite challenging but challenge promotes excellent work and that is achieved by our developers.

The app for Android was developed strictly under the updated technology and by shaking hand with IT advances to keep an app up-to-date and to promote its usage and to increase functionality and performance. There is no compromise adjusted in terms of quality.