This is only happening on fc14. fc12, CentOS, OS X, Solaris, x86, etc. do not have this problem.
Program received signal SIGSEGV, Segmentation fault.
0x00000034bb828f26 in XtIsManaged () from /usr/lib64/libXt.so.6
(gdb) where
#0 0x00000034bb828f26 in XtIsManaged () from /usr/lib64/libXt.so.6
#1 0x000000000040e3bd in cldhgtw_isUp () at nmap_cldhgtw.c:800
#2 0x000000000040e4ce in cldhgtw_refresh (make_new=0 '\000') at nmap_cldhgtw.c:884
#3 0x000000000043d731 in mcanvw_exposeCb (wid=0x150ae8e0, clnt=0x0,
call=0x7fffffff59e0) at nmap_mcanvw.c:750
#4 0x00000034bb81393f in XtCallCallbackList () from /usr/lib64/libXt.so.6
#5 0x00007ffff7bb85b4 in ?? () from /usr/lib64/openmotif/libXm.so.4
#6 0x00000034bb821b22 in XtDispatchEventToWidget () from /usr/lib64/libXt.so.6
#7 0x00000034bb82226e in ?? () from /usr/lib64/libXt.so.6
#8 0x00000034bb821344 in XtDispatchEvent () from /usr/lib64/libXt.so.6
#9 0x00007ffff7c51698 in XmUpdateDisplay () from /usr/lib64/openmotif/libXm.so.4
#10 0x000000000063d4b0 in NxmWarn_show (parent=0x152d4440,
message=0x7fffffff6070 "cannot load pixmap file /home/gempak/GEMPAK6.3.0/icons/nmap/turb00.xbm") at NxmWarn.c:78
NxmWarn_show (#10) should not be called - it's being called because XmGetPixmap is returning XmUNSPECIFIED_PIXMAP (value = 2) when the filename is valid and the file exists.
itempxm = XmGetPixmap ( XtScreen(parent),filename , fg, bg);
if ( itempxm == (Pixmap)XmUNSPECIFIED_PIXMAP ) {
sprintf ( warning, "cannot load pixmap file %s",
filename );
NxmWarn_show ( parent, warning );
itemwid[ii] = XtVaCreateManagedWidget ( itemtext[ii],
xmPushButtonWidgetClass, menu_bar,
NULL );
}
Again, this only happens with fc14:
uname -a
Linux ... 2.6.35.11-83.fc14.x86_64 #1 SMP Mon Feb 7 07:06:44 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
have tried rolling back to a number of openmotif/openmotif-devel versions with no luck:
openmotif-2.3.0-1
openmotif-2.3.1-1, etc.
thoughts?
Tue, 08/07/2012 - 14:43
#1
fc14 seg faults due to XmGetPixmap returning XmUNSPECIFIED_PIXMAP
building open motif from source solves this problem.
solution for motif developers: rebuild RPM packages against libX11-1.3.4-4 and things should go back to "working"
The problem is actually with libjpeg-turbo-1.1.0 library. After update from
1.0.1 to 1.1.0 binary compatibility was broken, so OpenMotif lib that was built
with libjpeg-turbo-1.0.1 can't work correctly. Please see
http://sourceforge.net/projects/libjpeg-turbo/forums/forum/1086868/topic...
discussion for details.
Possible workaround for now is to rebuild OpenMotif package with
libjpeg-turbo-1.1.0.
I have rebuilt OpenMotif from cvs with latest libjpeg-turbo; it would work with JPEG images, but not with PNG.
I have examined the bug and my fix is in Bugzilla.
http://bugs.motifzone.net/show_bug.cgi?id=1546
I hope this will be helpful to somebody.