cURL / Mailing Lists / curl-library / Single Mail


Re: Need ur help ASAP

From: Anjalinbenedicta J <>
Date: Thu, 1 Apr 2010 07:51:00 +0530
I have tested the memory leakage using dbx tool and find the below problem..
                Request a test. Expect success
dbx: warning: object file (unknown) was not compiled -g -- limited exception support
dbx: warning: can't find symbolic information for thrown type
Please assist me how to resolve this
Thanks ,
-----Ben Greear wrote: -----
To: libcurl development <>
From: Ben Greear <>
Date: 03/31/2010 08:18PM
cc: Anjalinbenedicta J <>
Subject: Re: Need ur help ASAP

On 03/31/2010 04:28 AM, Anjalinbenedicta J wrote:
>     Hi,
>     We are accessing our remote webserver using libcurl.We are using GET
>     method to post the request.The request is a simplified URL.We will
>     receive XML Response for the URL request.
>     *_Problem _*
>     When libcurl do DNS Cache look up gets timed out, our component is
>     getting crashed..
>     Can you please help me what would be the solution for this problem
>     at the earliest...
>     For Few Scenarios, The URL request is not being posted and our
>     component is killed abruptly.Can anyone pls help me what would be
>     the reason for this issue.It would be great if any one reply me the
>     quick response.
>     Thanks in anticipation
>     I Have attached the log below which will help to track the issue
>     clearly. our component is killed in the last statement of failure
>     scenario abruptly.

Run it under gdb or maybe valgrind and figure out the backtrace of
where it crashes.

Valgrind is nice because it will catch memory access errors before
the system crashes.


Ben Greear <>
Candela Technologies Inc
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

List admin:
Received on 2010-04-01