It is a bad idea on multi-user machines, so don't do it there. This is generally safe on single-user machines, though not ideal. Your X display can be made accessible to all local UNIX socket connections, including the ones from BOINC, by running The X display needs to be accessible to the BOINC graphics processes in order to see the interesting graphics for, e.g., and it isn't by default. Graphics are supported, but they won't show up by default. Thus, the following is only useful for very old version of boinc.) (Graphics processes seem to be forked from boincmgr now, with user's uid instead of boinc-client's uid, so it works by default. Make sure to have shut down the system-wide boinc_client by invoking "/etc/init.d/boinc-client stop" when debugging. This page has some detailed instructions how to run gdb. After its installation run boinc_client with the GNU Debugger gdb. Such are distributed with the boinc-dbg package. This only works for binaries that were compiled with the -g debug flag and are not stripped. A backtrace lists the functions that were called. SPARC and PowerPCs, some users have reported core dumps of the boinc client. The web site of the project features entries for each result which may be indicative of one problem or the other.Įxperiencing core dumps - how to get a backtrace with gdb That is performed by the binary downloaded dynamically by that client. The boinc-client installed by the Debian package does not perform the actual computation. The submitted results are not all 100% identical when run on different machines. If this is fewer than 10 in 100 times then this may be some physiological behaviour. Please note some information on this page may be out of date, and in need of updating.Įverything works fine but some submissions get evaluated as erroneous
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |