Tip: on Linux x86_64, if boinc 7.2.42 keeps dying with "buffer overflow" or "segmentation violation"

Message boards : Questions and problems : Tip: on Linux x86_64, if boinc 7.2.42 keeps dying with "buffer overflow" or "segmentation violation"
Message board moderation

To post messages, you must log in.

AuthorMessage
ChG

Send message
Joined: 13 Aug 16
Posts: 1
Germany
Message 71522 - Posted: 13 Aug 2016, 1:16:17 UTC

... you can try the following:

  • stop boinc:
    service boinc-client stop

  • become user boinc or root and go to /var/lib/boinc/ (or whatever working directory your boinc installation is configured to use)

  • move the two "client_state" files out of the way:
    mv client_state.xml      client_state.xml.old
    mv client_state_prev.xml client_state_prev.xml.old

  • restart boinc:
    service boinc-client start

and check whether it now works as expected.


Found out on OpenSuSE 13.2 with kernel 3.16.7-35-desktop and glibc-2.19-16.25.1.x86_64, where boinc 7.2.42 always ran into

...
13-Aug-2016 02:43:59 [---] Running CPU benchmarks
13-Aug-2016 02:43:59 [---] Suspending computation - CPU benchmarks in progress
*** buffer overflow detected ***: boinc terminated
======= Backtrace: =========
/lib64/libc.so.6(+0x7278f)[0x7f9a4e9d378f]
...


Hope this helps others having this.
Cheers
ID: 71522 · Report as offensive

Message boards : Questions and problems : Tip: on Linux x86_64, if boinc 7.2.42 keeps dying with "buffer overflow" or "segmentation violation"

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.