[Reconnoiter-users] HTTPS Seg fault

Theo Schlossnagle jesus at omniti.com
Tue Jul 14 17:42:44 EDT 2009


The ASYNC-ness, as you put it, does make groking the code very hard.   
Even with comments, consider it a rubiks cube for the mind :-)

On Jul 14, 2009, at 5:38 PM, Dan Di Spaltro wrote:

> It doesn't help just using the certificate generated from your make
> command in the test directory.  I am looking at your compared to the
> serf_get.c in the serf test directory and I don't see a whole lot of
> difference, but I can't pinpoint what is wrong.  I can definitely tell
> that setup_request is not getting run.  Again, the problem isn't clear
> yet.
>
> Best,
>
> On Tue, Jul 14, 2009 at 2:18 PM, Theo Schlossnagle<jesus at omniti.com>  
> wrote:
>> On Jul 14, 2009, at 2:53 PM, Dan Di Spaltro wrote:
>>>
>>> I submitted a ticket on the HTTPS check segfaulting.  I was  
>>> curious, do
>>> I need to add a certificate file or ca_chain, could that be reason  
>>> for
>>> the segfault.  It doesn't sound like in the docs that would be the
>>> reason but I couldn't figure it out from the code.  I am having a
>>> pretty hard time debugging some of this code with all the async-ness
>>> of the HTTP requests.  I think I need to learn how to use serf.
>>>
>>> * https://labs.omniti.com/trac/reconnoiter/ticket/156
>>
>>
>> Is that every time you use it?  I don't think I've run into that same
>> problem.  Does adding a ca_chain help?  A certificate should  
>> certainly not
>> be required -- that's for client auth.
>>
>> --
>> Theo Schlossnagle
>> http://omniti.com/is/theo-schlossnagle
>> p: +1.443.325.1357 x201   f: +1.410.872.4911
>>
>>
>>
>>
>>
>>
>
>
>
> -- 
> Dan Di Spaltro

--
Theo Schlossnagle
http://omniti.com/is/theo-schlossnagle
p: +1.443.325.1357 x201   f: +1.410.872.4911







More information about the Reconnoiter-users mailing list