|
From: Max <sur...@gm...> - 2012-12-25 16:59:59
|
apache fails to start with valgrind sudo valgrind --tool=memcheck --leak-check=full --trace-syscalls=yes -v --log-file=mylog.txt /home/y/bin/apache -X -f /home/y/conf/apache/apache.conf Log file says: ==24987== Conditional jump or move depends on uninitialised value(s) ==24987== at 0x4352D28: __umoddi3 (in /home/y/lib/libcrypto.so. 108) ==24987== by 0x42AC100: BN_mod_word__tps (in /home/y/lib/ libcrypto.so.108) ==24987== by 0x42AF65E: probable_prime (in /home/y/lib/ libcrypto.so.108) --24987-- used_suppression: 2131 U1004-ARM-_dl_relocate_ object ==24987== ==24987== ERROR SUMMARY: 3603022 errors from 1461 contexts (suppressed: 2131 from 15) |
|
From: John R. <jr...@bi...> - 2012-12-25 19:53:51
|
On 12/25/2012 08:55 AM, Max wrote:
> apache fails to start with valgrind
No, the report that you posted shows that apache has been running for a long time:
enough to generate 3,603,022 errors. If apache has any timeouts associated
with starting up, then there's a good chance that finding and suppressing
all those errors has consumed the timeout. (What was the wall-clock duration
of the run with 3603022 errors?)
> sudo valgrind --tool=memcheck --leak-check=full
> --trace-syscalls=yes -v --log-file=mylog.txt
> /home/y/bin/apache
> -X -f /home/y/conf/apache/apache.conf
>
> Log file says:
> ==24987== Conditional jump or move depends on uninitialised value(s)
> ==24987== at 0x4352D28: __umoddi3 (in /home/y/lib/libcrypto.so.
> 108)
> ==24987== by 0x42AC100: BN_mod_word__tps (in /home/y/lib/
> libcrypto.so.108)
> ==24987== by 0x42AF65E: probable_prime (in /home/y/lib/
> libcrypto.so.108)
> --24987-- used_suppression: 2131 U1004-ARM-_dl_relocate_
> object
> ==24987==
> ==24987== ERROR SUMMARY: 3603022 errors from 1461
> contexts (suppressed: 2131 from 15)
Search the web for "valgrind libcrypto.so apache" and find:
14. Why does Valgrind complain about the use of uninitialized data?
Follow the directions given there, and similarly for other crypto libraries.
After you have "tamed" the crypto code, then look at the errors that are
counted by "suppressed: 2131 from 15". If there are any real surprises,
then deal with those, too.
Finally, post again if/when there is something interesting.
--
|