DOUG Seg Fault

Obviously, segmentation faults can be for lots of reasons. Try the following. If you find other problems or solutions, please add them!

NVIDIA driver version

Check your NVIDIA driver version and make sure you aren't running into issue 00205

Direct Rendering

If you are using EDGE >= v1.1, try running "gde.csh" to see the graphic environment.

Make sure that it reports "direct rendering: Yes". If it reports "No", make sure you aren't using a remote display (ssh'd into another machine) and that your NVIDIA driver is installed correctly. You can also try reinstalling/upgrading your NVIDIA driver.

Make sure selinux is disabled or configured correctly

Unless you know how to get all of your selinux ducks in a row, running selinux will likely cause problems. Disable it by editing /etc/selinux/config and setting SELINUX=disabled and reboot.

Are you running the NVIDIA 295.xx driver?

There has been at least one report of seg faults on startup that went away downgrading to a 290.xx driver. Not enough data on this yet, but worth noting.

Check for RgbPath problems

We have seen very odd behavior if RgbPath is defined in the xorg.conf file when it shouldn't be (most new installations don't need this line) or if it is configured incorrectly. Try removing the line if it is there or making sure it is set up correctly in your xorg.conf file.

System updates

Sometimes updates from machines (such as yum automatic updates or Redhat's "up2date" utility) can sometimes revert to other graphics drivers or mess around with graphics libraries. If you notice DOUG seg-faulting after an update, try the following:

• Check to make sure you are still running the nvidia driver and not the open-source driver. You can check this by making sure you are still getting the nvidia splash screen when X starts.

• Try reinstalling the NVIDIA driver. Some users have reported reinstallation of the same NVIDIA driver version after a system update can fix the problem. To see what NVIDIA driver version you are running:

  cat /proc/driver/nvidia/version

Earth and Moon Map files

We recommend to people that the gisdata stuff be local to the machine running DOUG. One reason is for performance: reading and writing the data to a network mounted filesystem can slow things down. Another is to avoid collisions. If 3 doug clients are all running on seperate machines and are pointing to the same set of gisdata, then they will be hammering the network to read the file at the same time.

But the worse part is if they are all writing to it. If you are seg-faulting on startup, it could be because of problems with handling the gisdata. Try the following:

• Make your gisdata local (such as /dougdata/gisdata). This can solve problems and help performance.
• Make your gisdata earth.map file read-only. This doesn't need to be writeable unless you are trying to pull in higher-res imagery for specific areas. This can also help performance.

Verbose

Try running edge with the "-verbose" switch. Often times this will print out with a finer level of granularity allowing you to see exactly what step is causing the seg fault.