Forum > Linux

SIGSEGV: Segmentation violation using new 2.4 app

(1/1)

Urs Echternacht:
Hi,
have a problem with the new optimized Multi-Beam application (SSE3-Intel P4/PD Kernel 2.6) running Suse Linux 10.2 (32bit) on a Core2T7200. The hostid at Seti is 3680470 and an example result*. Will use with that host the SSE2-Intel P4 Kernel 2.6 version which seems to work.

*
CPU time 2.012125
stderr out <core_client_version>5.8.16</core_client_version>
<![CDATA[
<message>
process exited with code 131 (0x83)
</message>
<stderr_txt>
SIGSEGV: segmentation violation
Stack trace (11 frames):
setiathome-5.15.i686-pc-linux-gnu(boinc_catch_signal+0x5d)[0x80f28fd]
[0xb7f74420]
setiathome-5.15.i686-pc-linux-gnu[0x8103394]
setiathome-5.15.i686-pc-linux-gnu[0x80fdd38]
setiathome-5.15.i686-pc-linux-gnu[0x80fd533]
setiathome-5.15.i686-pc-linux-gnu[0x80fe23c]
setiathome-5.15.i686-pc-linux-gnu[0x8082d57]
setiathome-5.15.i686-pc-linux-gnu[0x8082861]
setiathome-5.15.i686-pc-linux-gnu[0x80eea8c]
/lib/libc.so.6(__libc_start_main+0xdc)[0xb7df4f9c]
setiathome-5.15.i686-pc-linux-gnu(pthread_mutex_unlock+0xe5)[0x804c581]

Exiting...
</stderr_txt>
]]>



edit:
FIXED, thanks.

Raistmer:
Got it, thanks :)
I see, your FTP full of useful stuff already :) Will look into it gradualy :)

Navigation

[0] Message Index