Thread 'Boinc-6.12.26 in Gentoo, buffer overflow'
Message boards : Questions and problems : Boinc-6.12.26 in Gentoo, buffer overflow
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 28 Oct 07 Posts: 10 |
I recently upgraded Boinc on my Gentoo Linux machine from 6.10.48 to 6.12.26. However, when running the client it immediately errors out with the following: 25-May-2011 21:26:05 [---] Starting BOINC client version 6.12.26 for x86_64-pc-linux-gnu 25-May-2011 21:26:05 [---] log flags: file_xfer, sched_ops, task 25-May-2011 21:26:05 [---] Libraries: libcurl/7.20.0 OpenSSL/0.9.8o zlib/1.2.5 25-May-2011 21:26:05 [---] Data directory: /home/klarsen 25-May-2011 21:26:05 [---] Processor: 4 AuthenticAMD AMD Phenom(tm) II X4 940 Processor [Family 16 Model 4 Stepping 2] 25-May-2011 21:26:05 [---] Processor: 512.00 KB cache 25-May-2011 21:26:05 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cm 25-May-2011 21:26:05 [---] OS: Linux: 2.6.37-gentoo-r4 25-May-2011 21:26:05 [---] Memory: 3.87 GB physical, 3.73 GB virtual 25-May-2011 21:26:05 [---] Disk: 116.39 GB total, 4.35 GB free 25-May-2011 21:26:05 [---] Local time is UTC +2 hours 25-May-2011 21:26:05 [---] NVIDIA GPU 0: GeForce GTS 450 (driver version unknown, CUDA version 3020, compute capability 2.1, 512MB, 401 GFLOPS peak) 25-May-2011 21:26:05 [---] No general preferences found - using BOINC defaults 25-May-2011 21:26:05 [---] Preferences: 25-May-2011 21:26:05 [---] max memory usage when active: 1981.70MB 25-May-2011 21:26:05 [---] max memory usage when idle: 3567.06MB *** buffer overflow detected ***: boinc_client terminated ======= Backtrace: ========= /lib64/libc.so.6(__fortify_fail+0x47)[0x7f17f61322a7] /lib64/libc.so.6(+0xe6150)[0x7f17f6130150] /lib64/libc.so.6(+0xe5529)[0x7f17f612f529] /lib64/libc.so.6(_IO_default_xsputn+0x91)[0x7f17f60bb931] /lib64/libc.so.6(_IO_vfprintf+0x33e4)[0x7f17f608fbe4] /lib64/libc.so.6(__vsprintf_chk+0x85)[0x7f17f612f5c5] /lib64/libc.so.6(__sprintf_chk+0x7f)[0x7f17f612f4ff] /usr/lib64/libboinc.so.6(_Z8dir_sizePKcRdb+0x133)[0x7f17f7868513] /usr/lib64/libboinc.so.6(_Z8dir_sizePKcRdb+0x14f)[0x7f17f786852f] ======= Memory map: ======== 00400000-004b4000 r-xp 00000000 08:03 563251 /usr/bin/boinc_client 006b3000-006b4000 r--p 000b3000 08:03 563251 /usr/bin/boinc_client 006b4000-006b5000 rw-p 000b4000 08:03 563251 /usr/bin/boinc_client 006b5000-006c1000 rw-p 00000000 00:00 0 009de000-00a61000 rw-p 00000000 00:00 0 [heap] 7f17f4826000-7f17f4fb3000 r-xp 00000000 08:03 965256 /usr/lib64/libcuda.so.260.19.36 7f17f4fb3000-7f17f51b2000 ---p 0078d000 08:03 965256 /usr/lib64/libcuda.so.260.19.36 7f17f51b2000-7f17f527e000 rw-p 0078c000 08:03 965256 /usr/lib64/libcuda.so.260.19.36 7f17f527e000-7f17f52a2000 rw-p 00000000 00:00 0 7f17f52a2000-7f17f52ad000 r-xp 00000000 08:03 415560 /lib64/libnss_files-2.12.2.so 7f17f52ad000-7f17f54ad000 ---p 0000b000 08:03 415560 /lib64/libnss_files-2.12.2.so 7f17f54ad000-7f17f54ae000 r--p 0000b000 08:03 415560 /lib64/libnss_files-2.12.2.so 7f17f54ae000-7f17f54af000 rw-p 0000c000 08:03 415560 /lib64/libnss_files-2.12.2.so 7f17f54af000-7f17f5637000 r-xp 00000000 08:03 48866 /usr/lib64/libcrypto.so.1.0.0 7f17f5637000-7f17f5837000 ---p 00188000 08:03 48866 /usr/lib64/libcrypto.so.1.0.0 7f17f5837000-7f17f5850000 r--p 00188000 08:03 48866 /usr/lib64/libcrypto.so.1.0.0 7f17f5850000-7f17f585a000 rw-p 001a1000 08:03 48866 /usr/lib64/libcrypto.so.1.0.0 7f17f585a000-7f17f585e000 rw-p 00000000 00:00 0 7f17f585e000-7f17f59c4000 r-xp 00000000 08:03 48867 /usr/lib64/libcrypto.so.0.9.8 7f17f59c4000-7f17f5bc3000 ---p 00166000 08:03 48867 /usr/lib64/libcrypto.so.0.9.8 7f17f5bc3000-7f17f5bd1000 r--p 00165000 08:03 48867 /usr/lib64/libcrypto.so.0.9.8 7f17f5bd1000-7f17f5bea000 rw-p 00173000 08:03 48867 /usr/lib64/libcrypto.so.0.9.8 7f17f5bea000-7f17f5bed000 rw-p 00000000 00:00 0 7f17f5bed000-7f17f5c3a000 r-xp 00000000 08:03 48873 /usr/lib64/libssl.so.0.9.8 7f17f5c3a000-7f17f5e39000 ---p 0004d000 08:03 48873 /usr/lib64/libssl.so.0.9.8 7f17f5e39000-7f17f5e3b000 r--p 0004c000 08:03 48873 /usr/lib64/libssl.so.0.9.8 7f17f5e3b000-7f17f5e41000 rw-p 0004e000 08:03 48873 /usr/lib64/libssl.so.0.9.8 7f17f5e41000-7f17f5e49000 r-xp 00000000 08:03 415786 /lib64/librt-2.12.2.so 7f17f5e49000-7f17f6048000 ---p 00008000 08:03 415786 /lib64/librt-2.12.2.so 7f17f6048000-7f17f6049000 r--p 00007000 08:03 415786 /lib64/librt-2.12.2.so 7f17f6049000-7f17f604a000 rw-p 00008000 08:03 415786 /lib64/librt-2.12.2.so 7f17f604a000-7f17f61a8000 r-xp 00000000 08:03 415749 /lib64/libc-2.12.2.so 7f17f61a8000-7f17f63a8000 ---p 0015e000 08:03 415749 /lib64/libc-2.12.2.so 7f17f63a8000-7f17f63ac000 r--p 0015e000 08:03 415749 /lib64/libc-2.12.2.so 7f17f63ac000-7f17f63ad000 rw-p 00162000 08:03 415749 /lib64/libc-2.12.2.so 7f17f63ad000-7f17f63b2000 rw-p 00000000 00:00 0 7f17f63b2000-7f17f63c8000 r-xp 00000000 08:03 831133 /lib64/libgcc_s.so.1 7f17f63c8000-7f17f65c7000 ---p 00016000 08:03 831133 /lib64/libgcc_s.so.1 7f17f65c7000-7f17f65c8000 r--p 00015000 08:03 831133 /lib64/libgcc_s.so.1 7f17f65c8000-7f17f65c9000 rw-p 00016000 08:03 831133 /lib64/libgcc_s.so.1 7f17f65c9000-7f17f664a000 r-xp 00000000 08:03 415787 /lib64/libm-2.12.2.so 7f17f664a000-7f17f6849000 ---p 00081000 08:03 415787 /lib64/libm-2.12.2.so 7f17f6849000-7f17f684a000 r--p 00080000 08:03 415787 /lib64/libm-2.12.2.so 7f17f684a000-7f17f684b000 rw-p 00081000 08:03 415787 /lib64/libm-2.12.2.so 7f17f684b000-7f17f6944000 r-xp 00000000 08:03 950223 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6.0.13 7f17f6944000-7f17f6b44000 ---p 000f9000 08:03 950223 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6.0.13 7f17f6b44000-7f17f6b4b000 r--p 000f9000 08:03 950223 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6.0.13 7f17f6b4b000-7f17f6b4d000 rw-p 00100000 08:03 950223 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6.0.13 7f17f6b4d000-7f17f6b62000 rw-p 00000000 00:00 0 7f17f6b62000-7f17f6b7a000 r-xp 00000000 08:03 1014984 /lib64/libpthread-2.12.2.so 7f17f6b7a000-7f17f6d79000 ---p 00018000 08:03 1014984 /lib64/libpthread-2.12.2.so 7f17f6d79000-7f17f6d7a000 r--p 00017000 08:03 1014984 /lib64/libpthread-2.12.2.so 7f17f6d7a000-7f17f6d7b000 rw-p 00018000 08:03 1014984 /lib64/libpthread-2.12.2.so 7f17f6d7b000-7f17f6d7f000 rw-p 00000000 00:00 0 7f17f6d7f000-7f17f6d95000 r-xp 00000000 08:03 978414 /lib64/libz.so.1.2.5 7f17f6d95000-7f17f6f95000 ---p 00016000 08:03 978414 /lib64/libz.so.1.2.5 7f17f6f95000-7f17f6f96000 r--p 00016000 08:03 978414 /lib64/libz.so.1.2.5 7f17f6f96000-7f17f6f97000 rw-p 00017000 08:03 978414 /lib64/libz.so.1.2.5 7f17f6f97000-7f17f6f99000 r-xp 00000000 08:03 415555 /lib64/libdl-2.12.2.so 7f17f6f99000-7f17f7199000 ---p 00002000 08:03 415555 /lib64/libdl-2.12.2.so 7f17f7199000-7f17f719a000 r--p 00002000 08:03 415555 /lib64/libdl-2.12.2.so 7f17f719a000-7f17f719b000 rw-p 00003000 08:03 415555 /lib64/libdl-2.12.2.so 7f17f719b000-7f17f71ef000 r-xp 00000000 08:03 48869 /usr/lib64/libssl.so.1.0.0 7f17f71ef000-7f17f73ef000 ---p 00054000 08:03 48869 /usr/lib64/libssl.so.1.0.0 7f17f73ef000-7f17f73f2000 r--p 00054000 08:03 48869 /usr/lib64/libssl.so.1.0.0 7f17f73f2000-7f17f73f7000 rw-p 00057000 08:03 48869 /usr/lib64/libssl.so.1.0.0 7f17f73f7000-7f17f7444000 r-xp 00000000 08:03 1124761 /usr/lib64/libcurl.so.4.2.0 7f17f7444000-7f17f7643000 ---p 0004d000 08:03 1124761 /usr/lib64/libcurl.so.4.2.0 7f17f7643000-7f17f7645000 r--p 0004c000 08:03 1124761 /usr/lib64/libcurl.so.4.2.0 7f17f7645000-7f17f7646000 rw-p 0004e000 08:03 1124761 /usr/lib64/libcurl.so.4.2.0 7f17f7646000-7f17f7647000 rw-p 00000000 00:00 0 7f17f7647000-7f17f764d000 r-xp 00000000 08:03 1120040 /usr/lib64/libboinc_crypt.so.6.12.26 7f17f764d000-7f17f784c000 ---p 00006000 08:03 1120040 /usr/lib64/libboinc_crypt.so.6.12.26 7f17f784c000-7f17f784d000 r--p 00005000 08:03 1120040 /usr/lib64/libboinc_crypt.so.6.12.26 7f17f784d000-7f17f784e000 rw-p 00006000 08:03 1120040 /usr/lib64/libboinc_crypt.so.6.12.26 7f17f784e000-7f17f789f000 r-xp 00000000 08:03 1120037 /usr/lib64/libboinc.so.6.12.26 7f17f789f000-7f17f7a9e000 ---p 00051000 08:03 1120037 /usr/lib64/libboinc.so.6.12.26 7f17f7a9e000-7f17f7a9f000 r--p 00050000 08:03 1120037 /usr/lib64/libboinc.so.6.12.26 7f17f7a9f000-7f17f7aa0000 rw-p 00051000 08:03 1120037 /usr/lib64/libboinc.so.6.12.26 7f17f7aa0000-7f17f7aa2000 rw-p 00000000 00:00 0 7f17f7aa2000-7f17f7ac0000 r-xp 00000000 08:03 415553 /lib64/ld-2.12.2.so 7f17f7c8c000-7f17f7c94000 rw-p 00000000 00:00 0 7f17f7cbe000-7f17f7cbf000 r--s fc009000 00:10 5385 /dev/nvidia0 7f17f7cbf000-7f17f7cc0000 rw-p 00000000 00:00 0 7f17f7cc0000-7f17f7cc1000 r--p 0001e000 08:03 415553 /lib64/ld-2.12.2.so 7f17f7cc1000-7f17f7cc2000 rw-p 0001f000 08:03 415553 /lib64/ld-2.12.2.so 7f17f7cc2000-7f17f7cc3000 rw-p 00000000 00:00 0 7fffdf714000-7fffdf733000 rwxp 00000000 00:00 0 [stack] 7fffdf733000-7fffdf735000 rw-p 00000000 00:00 0 7fffdf7c4000-7fffdf7c5000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] SIGABRT: abort called Stack trace (14 frames): /usr/lib64/libboinc.so.6(boinc_catch_signal+0x4d)[0x7f17f7866a4d] /lib64/libpthread.so.0(+0xf870)[0x7f17f6b71870] /lib64/libc.so.6(gsignal+0x35)[0x7f17f607c775] /lib64/libc.so.6(abort+0x17f)[0x7f17f607daff] /lib64/libc.so.6(+0x6db12)[0x7f17f60b7b12] /lib64/libc.so.6(__fortify_fail+0x47)[0x7f17f61322a7] /lib64/libc.so.6(+0xe6150)[0x7f17f6130150] /lib64/libc.so.6(+0xe5529)[0x7f17f612f529] /lib64/libc.so.6(_IO_default_xsputn+0x91)[0x7f17f60bb931] /lib64/libc.so.6(_IO_vfprintf+0x33e4)[0x7f17f608fbe4] /lib64/libc.so.6(__vsprintf_chk+0x85)[0x7f17f612f5c5] /lib64/libc.so.6(__sprintf_chk+0x7f)[0x7f17f612f4ff] /usr/lib64/libboinc.so.6(_Z8dir_sizePKcRdb+0x133)[0x7f17f7868513] /usr/lib64/libboinc.so.6(_Z8dir_sizePKcRdb+0x14f)[0x7f17f786852f] Exiting... I do not know if this is a Gentoo specific error, or Boinc in general, which is why I have posted here too. I'd be happy to provide any debugging information needed, just ask. ID: 38002 ·  |
 Trog Dog Send message Joined: 6 May 06 Posts: 287 
|
G'day Kenneth Just upgraded 6 boxes as part of my usual weekly update (emerge -auvDN world) without problems - did you run etc-update and accept the changes? FYI my boxes are all stable tree AMD64 (4 plain vanilla service/daemon install) (2 with gpu where the boinc client is started from a terminal within gnome) I did try running the boinc manager on a couple of them without success (wouldn't connect to localhost) but that doesn't bother me as I manage them remotely from a win box using boincview - still nothing crashed. CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1 ID: 38025 · |
|
Send message Joined: 28 Oct 07 Posts: 10 |
I've finally got it working, and the error was probably due to my stupidity... If you look at the above log I'm trying to start the client from my home directory. However, under Gentoo boinc runs as user "boinc" which does not have access to that directory. Anyway, I completely wiped Boinc from my system, losing some 300h of a CPDN model and am now trying to connect to BAM which seems to be down momentarily (or I have a new problem on my hands...). ID: 38061 · |
|
Send message Joined: 28 Oct 07 Posts: 10 |
OK BAM is indeed down at the moment, I can attach projects manually. For any others who may run into the problem I've got: It seems that some project causes the memory allocation error when trying to start Boinc 6.12.26. For me, the solution was indeed to remove all files related to Boinc and reemerge. Even so, trying to run the client manually from anywhere outside /var/lib/boinc ALSO resulted in an error, hence my confusion. Anyway, thanks for your input here and at the Gentoo boards, Trog Dog! ID: 38062 · |
|
Send message Joined: 28 Oct 07 Posts: 10 |
No, as soon as I attach a project and let it run, I get the above error or even a segfault. Something's definitely messed up with this release... Is there any kind of debug info I can provide to help solve this problem? ID: 38063 · |
|
Trog Dog Send message Joined: 6 May 06 Posts: 287
|
25-May-2011 21:26:05 [---] Libraries: libcurl/7.20.0 OpenSSL/0.9.8o zlib/1.2.5 How come you have 2 versions of ssl? Also the current stable 64bit version is 1.0.0d from one of my boxes 31-May-2011 05:40:23 [---] Libraries: libcurl/7.20.0 OpenSSL/1.0.0d zlib/1.2.5 from my reading of the above your boinc was compiled against 0.9.8 but is also referencing 1.0.0 CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1 ID: 38066 · |
|
Send message Joined: 28 Oct 07 Posts: 10 |
Sorry for not having replied earlier, I've been ill for the last few days :( I've just checked, and I only have openssl 1.0.0 installed: equery list openssl [ Searching for package 'openssl' in all categories among: ] * installed packages [I--] [ ] dev-libs/openssl-1.0.0d (0) Anyway, I've got Boinc-6.12.26 to work with several projects, and am slowly adding more to find out which cause problems. So far I can only confirm that WCG causes the above error, as soon as I attach it. ID: 38125 · |
Jord Send message Joined: 29 Aug 05 Posts: 15640 
|
So far I can only confirm that WCG causes the above error, as soon as I attach it. WorldCommunityGrid uses secure HTTP (https) as its address. Could be your problem. Is port 443 allowed to communicate with the internet in your local firewall? ID: 38127 · |
|
Send message Joined: 5 Oct 06 Posts: 5149 
|
So far I can only confirm that WCG causes the above error, as soon as I attach it. Or, perhaps, it's the encryption required by HTTPS which invokes the call to SSL, and hence triggers the (failing) library access? ID: 38128 · |
|
Send message Joined: 28 Oct 07 Posts: 10 |
Is port 443 allowed to communicate with the internet in your local firewall? Yes, I tried disabling the firewall entirely before starting Boinc. ID: 38130 · |
|
Send message Joined: 28 Oct 07 Posts: 10 |
How can I check this? As I said, according to my system only version 1.0.0d of openssl is installed, and I've recompiled Boinc after any other system upgrades. ID: 38131 · |
|
Trog Dog Send message Joined: 6 May 06 Posts: 287
|
You can try running emerge -pavD --depclean see what it wants to clean up. Just checked my boxes and there is no reference to any previous versions of ssl in /usr/lib64 ls /usr/lib64/*ssl* /usr/lib64/libevent_openssl-2.0.so.5 /usr/lib64/libevent_openssl-2.0.so.5.0.1 /usr/lib64/libevent_openssl.la /usr/lib64/libevent_openssl.so /usr/lib64/libgnutls-openssl.a /usr/lib64/libgnutls-openssl.la /usr/lib64/libgnutls-openssl.so /usr/lib64/libgnutls-openssl.so.26 /usr/lib64/libgnutls-openssl.so.26.16.14 /usr/lib64/libssl.a /usr/lib64/libssl.so /usr/lib64/libssl.so.1.0.0 /usr/lib64/libssl.so.6 /usr/lib64/libssl3.so /usr/lib64/libssl3.so.12 I would open a thread on the gentoo forum as it's looking to me like a problem with your box and not an upstream issue. FWIW I would also do a full update check emerge -auvDN world eselect news read new etc-update elogv revdep-rebuild just in case something was missed or overlooked previously. ID: 38140 · |
Copyright © 2025 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.