Red Hat Bugzilla – Bug 163017
Crash linking with libGLw
Last modified: 2007-11-30 17:11:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328 Fedora/1.7.6-1.2.5
Description of problem:
Trying to port an OpenMotif/OpenGL application to the x86_64 architecture has thrown up a problem with libGLw. There appears to be something badly wrong internally with this library, such that just linking with it (not even using it) causes an immediate crash.
If compiled with the following
g++ -g motiftest.cpp -o motiftest -L/usr/X11R6/lib64 -lGL -lXm -lXmu -lXt -lX11
then the sample code runs perfectly.
If compiled with libGLW, e.g.
g++ -g motiftest.cpp -o motiftest -L/usr/X11R6/lib64 -lGLw -lGL -lXm -lXmu -lXt -lX11
then the sample code crashed within the XtVaCreateManagedWidget call.
Version-Release number of selected component (if applicable):
xorg-x11-devel-6.8.2-37 openmotif-devel-2.2.3-10 openmotif-2.2.3-10
Steps to Reproduce:
1. Compile with g++ -g motiftest.cpp -o motiftest -L/usr/X11R6/lib64 -lGLw -lGL -lXm -lXmu -lXt -lX11
2. Run ./motiftest
Actual Results: Application core-dumps within the internals of Xt.
Expected Results: It should have created the widget and continued.
Created attachment 116640 [details]
Sample code demonstrating problem
Same problem occurs on i386. The code works fine using FC2 and FC3.
Yes, openmotif includes a bundled version of libGLw which they have modified
in an incompatible way to the "official" libGLw which ships with X.Org. I
believe there have been updates released to address this openmotif bug.
Reassigning to openmotif component...
Nope, libGLw includes copies of openmotif headers.
Assigning back to xorg-x11.
*** Bug 161528 has been marked as a duplicate of this bug. ***
Adding to FC5Target for review.
Has anyone identified what the actual problem is?
Does you last comment mean that this will not be fixed for FC4?
(In reply to comment #7)
> Has anyone identified what the actual problem is?
Yes, see comment #4 above.
> Does you last comment mean that this will not be fixed for FC4?
It doesn't mean that, but in reality, that is probably true nonetheless.
Ultimately, what we'd like to do, is have libGLw and libGLU split out
of Mesa sources, as they really should be standalone rpm packages. Then,
we'd like to push at least libGLw to Fedora Extras, as nothing in the
distribution uses it now.
In the mean time, what is needed, is for someone to investigate the
libGLw build, remove the private openmotif headers, and restructure
the Makefiles or whatever to use the installed systemwide motif
headers instead. Then to produce a patch, test it, and commit it
to CVS. From there it will go into rawhide for a while to be
tested, and then theoretically make it into future FC5 and FC4
However, it is currently a low priority issue right now. It'll get
fixed eventually, but wether FC4 is still maintained or not by then
is another question. If someone cares strongly about the issue and
is interested in doing the legwork and attaches a patch that fixes
the problem however, that would seriously speed up the likelyhood
of this getting fixed in FC5 and FC4 sooner.
There's just too much going on in rawhide right now, and over 200
open bugs in bugzilla against X components, so unfortunately, many
issues will sit around for a while based on priority and other
Patches certainly welcome though, thanks for asking. ;)
Changing component to Mesa.
Need to verify that this is still happening with the latest libGLw.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
Mass closure: This bug has been in NEEDINFO for over six weeks with no
additional information provided, and is therefore being closed. If this bug is
still an issue for you, please supply the requested information, and reopen the bug.