John Nagle wrote:
> Heikki Toivonen wrote:
>> John Nagle wrote:
>>> Still having trouble reproducing the problem. But somewhere,
>>> something raised that bogus no-error exception three times.
>>> Anything that returns "(0, 'Error')" as exception data is a bug.
>>
>> If you can, build python an
Heikki Toivonen wrote:
> John Nagle wrote:
>> Still having trouble reproducing the problem. But somewhere,
>> something raised that bogus no-error exception three times.
>> Anything that returns "(0, 'Error')" as exception data is a bug.
>
> If you can, build python and m2crypto with debug sym
John Nagle wrote:
> Still having trouble reproducing the problem. But somewhere,
> something raised that bogus no-error exception three times.
> Anything that returns "(0, 'Error')" as exception data is a bug.
If you can, build python and m2crypto with debug symbols, and place
breakpoints in |
John Nagle wrote:
> John Nagle wrote:
>> I just "upgraded" from M2Crypto 0.17 to M2Crypto 0.18, and I'm
>> running my regression tests. I'm seeing occasional cases where
>> M2Crypto raises the exception SSL.SSLError, and the associated
>> error is "(0, 'Error')", which is the bogus error you get
John Nagle wrote:
> I just "upgraded" from M2Crypto 0.17 to M2Crypto 0.18, and I'm
> running my regression tests. I'm seeing occasional cases where
> M2Crypto raises the exception SSL.SSLError, and the associated
> error is "(0, 'Error')", which is the bogus error you get if you feed 0 to
> "per
I just "upgraded" from M2Crypto 0.17 to M2Crypto 0.18, and I'm
running my regression tests. I'm seeing occasional cases where
M2Crypto raises the exception SSL.SSLError, and the associated
error is "(0, 'Error')", which is the bogus error you get if you feed 0 to
"perror". It failed once on "v
