On 2 April 2013 11:36, Michael Wallner wrote:
> On 2 April 2013 08:50, Rasmus Lerdorf wrote:
>
>>
>> Looks like these ASN1_STRING_to_UTF8 ones are normal for libcrypto.
>> Really hard to debug openssl stuff with all these Valgrind false
>> positives. Still trying to track down the core on Centos
On 2 April 2013 11:36, Michael Wallner wrote:
> On 2 April 2013 08:50, Rasmus Lerdorf wrote:
>
>>
>> Looks like these ASN1_STRING_to_UTF8 ones are normal for libcrypto.
>> Really hard to debug openssl stuff with all these Valgrind false
>> positives. Still trying to track down the core on Centos
On 2 April 2013 08:50, Rasmus Lerdorf wrote:
>
> Looks like these ASN1_STRING_to_UTF8 ones are normal for libcrypto.
> Really hard to debug openssl stuff with all these Valgrind false
> positives. Still trying to track down the core on Centos 6.2. Looks like
> a weird build issue at this point.
>
On 04/01/2013 07:49 PM, Rasmus Lerdorf wrote:
> ==12085== Uninitialised value was created by a stack allocation
> ==12085==at 0x7B54530: ASN1_STRING_to_UTF8 (in
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
Looks like these ASN1_STRING_to_UTF8 ones are normal for libcrypto.
Really hard to debu
On 04/01/2013 07:49 PM, Rasmus Lerdorf wrote:
> This standalone self-contained test script segfaults on Centos 6.2 for
> me with PHP 5.4:
>
> https://gist.github.com/anonymous/5289189
Oops, the script gist is actually:
https://gist.github.com/anonymous/526
-Rasmus
--
PHP Internals - PHP R
