astropulse segmentation violation

Questions and Answers : Unix/Linux : astropulse segmentation violation
Message board moderation

Author	Message
David Anderson (not *that* DA) Send message Joined: 5 Dec 09 Posts: 215 Credit: 74,008,558 RAC: 74	Message 1037851 - Posted: 1 Oct 2010, 17:29:45 UTC Astropulse gets a segmentation violation consistently. Ubuntu 10.04, Intel Core Duo. Nvidia N9500GT. glibc 2.11.1 Suggestions on how to either avoid the segv or avoid astropulse? ID: 1037851 ·
Jord Volunteer tester Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3	Message 1037858 - Posted: 1 Oct 2010, 17:38:15 UTC - in response to Message 1037851.   Last modified: 1 Oct 2010, 17:39:55 UTC Avoid Astropulse? Your Computer -> Seti@Home preferences -> Edit -> check only Seti@Home Enhanced, uncheck "If no work for selected applications is available, accept work from other applications?" -> Save changes to the web site. At the next time your BOINC contacts Seti, it'll use those preferences. As for "process got signal 11", see this FAQ. ID: 1037858 ·
David Anderson (not *that* DA) Send message Joined: 5 Dec 09 Posts: 215 Credit: 74,008,558 RAC: 74	Message 1037871 - Posted: 1 Oct 2010, 17:59:34 UTC - in response to Message 1037858.   Thanks. I just realized (looking at task pages on Seti website) that while Astropulse almost always segv's it has completed on a couple of occasions (credit pending verification). ID: 1037871 ·
David Anderson (not *that* DA) Send message Joined: 5 Dec 09 Posts: 215 Credit: 74,008,558 RAC: 74	Message 1037888 - Posted: 1 Oct 2010, 18:26:27 UTC - in response to Message 1037871.   Changed preferences to avoid astropulse. Again, thanks for the tip. Just FYI, 14 astropulse tasks got Signal 11, 2 completed and are pending verification. ap_client_version 6.10.17 Many had Signal 11 failures after 10+ chunks (mainloop()), a few failed on the first chunk. ID: 1037888 ·
Jord Volunteer tester Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3	Message 1037965 - Posted: 1 Oct 2010, 21:25:27 UTC - in response to Message 1037888.   Could be it's just something that doesn't like your computer or Linux distro's kernel version. But difficult to trace, as are all segvaults. ID: 1037965 ·
David Anderson (not *that* DA) Send message Joined: 5 Dec 09 Posts: 215 Credit: 74,008,558 RAC: 74	Message 1038146 - Posted: 2 Oct 2010, 2:59:17 UTC - in response to Message 1037965.   Yup. Been tracing Unix segfaults since ~1980 and some of them have been very very difficult to understand. Some of them my own fault :-) ID: 1038146 ·

 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.