On Sun, Aug 16, 2009 at 6:11 PM, Brandon Tate <brandonntate_at_gmail.com>wrote:

>
> On Aug 16, 2009, at 5:49 PM, Kamil Dudka wrote:
>
> On Sunday 16 of August 2009 23:43:31 Brandon Tate wrote:
>>
>>> I've been messing around quite a bit and have made some discoveries.
>>>
>>> 1) Can run examples from the command line (used google.com).
>>> 2) Cgi doesn't crash if no URL Option is set.
>>>
>>> So, why would curl just die if a URL is set. Other options can be set
>>> without an issue. Maybe a permissions issue with outgoing connections
>>> in the cgi? Not sure how I would go about checking that. Any insight/
>>> suggestions?
>>>
>>
>> There can be different libraries used from the command line and different
>> from
>> the CGI script. Yes, there might be also a problem with permissions. But I
>> have no experiences with CGI yet. Maybe someone else could give an advice.
>>
>> But at first you need to discover how does it die. Maybe you want to dig
>> some
>> CGI logs?
>
>
Have you tried to strip all options (except the URL) and then see if it
crashes. You
mentionned in curlpp mailing-list that the examples were working. So, if
your CGI
crashes even though no options other that the URL is set, then it's 99% sure

that you got a library linking problem.

>
>>
>> Kamil
>>
>
> Nothing prints to the logs when it dies. That's what's been driving us
> crazy. We can't find any information. All we know is it dies at perform()
> and only when a url is set. I'm just looking for common causes we could
> check at this point.
>
>
Received on 2009-08-17