[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: valgrind complaints on curl with libidn

From: Kamil Dudka
Subject: Re: valgrind complaints on curl with libidn
Date: Mon, 24 Oct 2011 00:22:46 +0200
User-agent: KMail/1.9.10

On Sunday 23 October 2011 23:53:04 Daniel Stenberg wrote:
> ==17087== Invalid read of size 4
> ==17087==    at 0x4043967: idna_to_ascii_4z (idna.c:519)
> ==17087==    by 0x4043BF4: idna_to_ascii_8z (idna.c:570)
> ==17087==    by 0x808237B: resolve_server (url.c:4572)
> ==17087==    by 0x808331A: create_conn (url.c:5063)
> ==17087==    by 0x80835A0: Curl_connect (url.c:5194)
> ==17087==    by 0x808F3A9: connect_host (transfer.c:1988)
> ==17087==    by 0x808F683: Curl_do_perform (transfer.c:2126)
> ==17087==    by 0x808F9E9: Curl_perform (transfer.c:2272)
> ==17087==    by 0x8064DCD: curl_easy_perform (easy.c:537)
> ==17087==    by 0x805A551: operate (tool_operate.c:1217)
> ==17087==    by 0x8055F30: main (tool_main.c:92)

This is a known issue:

You can try to recompile libidn with -fno-builtin-strlen or tweak the gcc 
optimization flags in another way.  There is no available fix/workaround
for valgrind I would be aware of.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]