I´ve got an segmentation violation on 2 machines. one machine is running OpenSuse 10.1 preconfigured by the web hoster on an intel cpu, the other one is running OpenSuse 10.3 X64 on AMD using 32-Bit client.
Both machines went well for serveral weeks, the AMD crashed while seti was running, and a few hours later the intel, also while seti was running.
i deleted everything belonging to boinc and installed the most current release (5.10.28 32bit) on both machines, added climateprediction on the amd, fine. added seti on the amd: segfault. added seti on the intel (used to be the only application there): segfault.

since the faults are on 2 machines maintained by different people, one of the releases installed serveral hundret times, and they faulted after running 4 weeks, with serveral hours distance in time, i guess thats a problem of seti, maybe together with special workunits.

what should i do?

It happened again: the AMD (who knows why, it should be detached from seti) connected to seti for a download, then started seti and segfaulted.

---

The SETI application works for the most systems without any problems.
I think, that the crashes your systems had is not normal.
Eventualy some libraries are not installed on the AMD system.
Your Intel system produces some invalid results. - Eventualy a hardware test would be needed.
Could you please post the output from the BOINC client of both systems, if the error happens.
Also the output of the command "ldd $BOINC_DIR/projects/setiathome*/setiathome*" would be very helpfull.

---