From chirpinternet:
We've had to disable the pagespeed module following install of 1.6.29.4 as the
server started Segfaulting every time curl_exec() was called from
PHP (every 10 minutes via CRON). We skipped 1.6.29.3, but earlier versions
didn't have this problem. Reenable the module and the problem returns
immediately.
Original issue reported on code.google.com by sligocki@google.com on 25 Jul 2013 at 3:00
The text was updated successfully, but these errors were encountered:
Fixed in r3332 and ported into latest beta 1.6.29.5.
More details from Maks:
Well, we generally use hidden visibility to avoid that; but looking at objdump
there may be a few symbols that are leaking out:
objdump -T //usr/lib/apache2/modules/mod_pagespeed.so |grep -v "UND" |
grep -v _Z
000000000013b6e0 g DF .text 0000000000000626 Base aesni_xts_encrypt
0000000000143180 g DF .text 0000000000001275 Base
sha256_block_data_order
000000000013bd10 g DF .text 00000000000006af Base aesni_xts_decrypt
0000000000912c7e g D *ABS* 0000000000000000 Base _edata
000000000013a5c0 g DF .text 0000000000000031 Base aesni_encrypt
000000000013a600 g DF .text 0000000000000031 Base aesni_decrypt
000000000013f300 g DF .text 000000000000030e Base gcm_ghash_clmul
0000000000138230 g DF .text 0000000000000037 Base
private_AES_set_encrypt_key
00000000008fb140 g DO .data 0000000000000068 Base
pagespeed_module /// the one we actually want exported
0000000000138170 g DF .text 00000000000000b8 Base AES_decrypt
000000000013b300 g DF .text 00000000000003da Base
aesni_ctr32_encrypt_blocks
,,,,
I wonder if they are in ASM or something.
Original comment by sligocki@google.com on 25 Jul 2013 at 3:02
Original issue reported on code.google.com by
sligocki@google.com
on 25 Jul 2013 at 3:00The text was updated successfully, but these errors were encountered: