Message boards :
Number crunching :
Memory Allocation problem
Message board moderation
| Author | Message |
|---|---|
 AnanasSend message Joined: 17 Jul 05 Posts: 102 Credit: 542,016 RAC: 0 |
w1jul_niebb1d__24__s__64.28_59.31__9.8_10__6__19_1_sixvf_boinc41760_0 Message : Das Segment ist bereits gelöscht und kann nicht gesperrt werden. (0x9d) - exit code 157 (0x9d) (segment has already been deleted (="free'd" I guess) and cannot be locked) |
 Send message Joined: 18 Sep 04 Posts: 163 Credit: 1,682,370 RAC: 0 |
Hi Ananas, had sth. similar: SIGSEGV's on Linux. <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> process got signal 11 </message> <stderr_txt> forrtl: error (78): process killed (SIGTERM) Stack trace terminated abnormally. forrtl: error (78): process killed (SIGTERM) Stack trace terminated abnormally. forrtl: error (78): process killed (SIGTERM) Stack trace terminated abnormally. forrtl: error (78): process killed (SIGTERM) Stack trace terminated abnormally. </stderr_txt> ]]> http://lhcathomeclassic.cern.ch/sixtrack/result.php?resultid=3709054 Michael Team Linux Users Everywhere 
|
©2025 CERN