There is actually a new stack trace I obtained through the core dump.
This occurs sometimes too along with the ones previously mentioned in
the earlier mail. Interestingly enough all of them occur in the
curl_easy_cleanup. Is there any workaround to this?
Thanks,
-Sachin

Type 'help' for help.
reading symbolic information ...
[using memory image in core]

Segmentation fault in ConnectionKillOne at line 1678 in file "" ($t1)
couldn't read "url.c"

(dbx) where
ConnectionKillOne(data = 0x213c035c), line 1678 in "url.c"
Curl_close(data = 0x213c035c), line 206 in "url.c"
curl_easy_cleanup(0x213c035c), line 394 in "easy.c"
getMMValueSql(0x212ebafd), line 487 in "das.c"

On Mon, 1 Nov 2004 17:17:40 -0700, Sachin Mahajan
<sachin.k.mahajan_at_gmail.com> wrote:
> I think you are right. Is there any alternative? This happens when I
> try to upload large pdf files(not more then 600k though). Is there any
> workaround for the cleanup(realloc)
> Thanks,
> -Sachin
>
>
>
>
> On Mon, 1 Nov 2004 11:07:50 +0100 (CET), Daniel Stenberg
> <daniel-curl_at_haxx.se> wrote:
> > On Fri, 29 Oct 2004, Sachin Mahajan wrote:
> >
> > > I am getting a core dump on curl_easy cleanup when using the latest
> > > version of libcurl on aix.
> > > Following is the code:
> > >
> > > chunk.memory=NULL; /* we expect realloc(NULL, size) to work */
> >
> > So, does AIX really allow realloc() on NULL? I found some web pages on the net
> > suggesting otherwise. Can you verify this?
> >
> > --
> > Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
> > Dedicated custom curl help for hire: http://haxx.se/curl.html
> >
>
Received on 2004-11-02