Message boards : Number crunching : Segmentation violation
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Toby

Send message
Joined: 1 Sep 04
Posts: 137
Credit: 1,482,744
RAC: 5,070
Message 20655 - Posted: 13 Oct 2008, 13:43:21 UTC
Last modified: 13 Oct 2008, 13:43:41 UTC

I just came in to work to find my boinc had crashed again just after midnight on October 12th. It looks like the log may have caught it in the act this time:

12-Oct-2008 00:11:21 [lhcathome] Sending scheduler request: To fetch work. Requesting 84377 seconds of work, reporting 0 completed tasks
12-Oct-2008 00:11:26 [lhcathome] Scheduler request succeeded: got 0 new tasks
12-Oct-2008 00:21:48 [lhcathome] Starting pì~E
SIGSEGV: segmentation violation
Stack trace (12 frames):
/usr/bin/boinc_client[0x46cc29]
/lib/libpthread.so.0[0x2b329c38bed0]
/lib/libc.so.6(strstr+0x19)[0x2b329c88e309]
/usr/bin/boinc_client[0x479a6a]
/usr/bin/boinc_client[0x443b83]
/usr/bin/boinc_client[0x413898]
/usr/bin/boinc_client[0x413f71]
/usr/bin/boinc_client[0x4314ff]
/usr/bin/boinc_client[0x422339]
/usr/bin/boinc_client[0x4516d4]
/lib/libc.so.6(__libc_start_main+0xf4)[0x2b329c837b74]
/usr/bin/boinc_client(__gxx_personality_v0+0x1a9)[0x404909]

Exiting...


It seems to have died while printing the line I hilighted in red. The three characters after the p are actually a two byte sequence of gibberish (when viewed in a hex editor: EC and 85) and I'm wondering if the p is actually gibberish as well... usually that line prints the name of the work unit being started, like this:

11-Oct-2008 23:29:04 [lhcathome] Starting wl55fs_l55f__3__64.3175_59.3275__20_22__6__70_1_sixvf_boinc416043_3

but I don't think any of the projects I'm attached to on this machine have work unit names that start with a p...
- A member of The Knights Who Say NI!
My BOINC stats site
ID: 20655 · Report as offensive     Reply Quote
AdeB
Avatar

Send message
Joined: 9 Dec 06
Posts: 9
Credit: 2,413,908
RAC: 0
Message 20724 - Posted: 30 Oct 2008, 17:03:39 UTC

And it happened again:

30-Oct-2008 09:41:18 [lhcathome] Sending scheduler request: To fetch work. Requesting 714 seconds of work, reporting 0 completed tasks
30-Oct-2008 09:41:23 [lhcathome] Scheduler request succeeded: got 0 new tasks
30-Oct-2008 09:56:37 [lhcathome] Sending scheduler request: To fetch work. Requesting 716 seconds of work, reporting 0 completed tasks
30-Oct-2008 09:56:42 [lhcathome] Scheduler request succeeded: got 0 new tasks
30-Oct-2008 10:11:56 [lhcathome] Sending scheduler request: To fetch work. Requesting 1853 seconds of work, reporting 1 completed tasks
30-Oct-2008 10:12:02 [lhcathome] Scheduler request succeeded: got 0 new tasks
SIGSEGV: segmentation violation
Stack trace (8 frames):
/usr/bin/boinc_client[0x80b7ee0]
[0xffffe420]
/usr/bin/boinc_client[0x8077b7c]
/usr/bin/boinc_client[0x8068f6d]
/usr/bin/boinc_client[0x809b68b]
/usr/bin/boinc_client[0x809ba19]
/lib/libc.so.6(__libc_start_main+0xdc)[0xb7b60fdc]
/usr/bin/boinc_client(__gxx_personality_v0+0x115)[0x804b411]

Exiting...


The last change to this log-file was at 10:12, so the segmentation violation occurred immediately after boinc contacted lhcathome.

AdeB
ID: 20724 · Report as offensive     Reply Quote
Previous · 1 · 2

Message boards : Number crunching : Segmentation violation


©2023 CERN