NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
On Thu, Apr 7, 2011 at 4:56 PM, Michael James <mjames@xxxxxxxxxxxxxxxx> wrote: > I'm running Gempak on a Fedora 14 x64 system and I'm having problems with > Nmap2. Whenever I click on Nmap2 from the NTL programs list or run nmap2 > from the command line I immediately get a dialog box that says warning and > Nmap2 then gives a segmentation fault. Running nmap2 with the gdb debugger > reveals that there is a segmentation fault in "0x0000003665428f26 in > XtIsManaged () from /usr/lib64/libXt.so.6". Can someone please help me, as > this is a problem that started only recently and I suspect a recent update > from Fedora Updates is causing this. > For what it's worth, it looks like libXt-1.0.7-1 has been the only version of libXt in Fedora 14. 1.0.6-3 was in Fedora 12, and I ran nmap2 against that build and it didn't seem to make a difference. I haven't had a chance to play with it any further, but I wonder if the libXt.so.6 error is a red herring. Has anyone else had any luck with this? -- Ben Cotton Systems Research Engineer IT Research Systems Purdue University
gembud archives: