On Wed, Sep 12, 2007 at 12:28:09PM +0200, Tor Arntsen wrote:
> The 'calloc' call itself is an illegal address. Valgrind seems to agree:
> ==21263== Jump to the invalid address stated on the next line
> ==21263== at 0x2FFF204: ???
> ==21263== by 0x8049141: test (lib540.c:123)
> ==21263== by 0x8049366: main (first.c:85)
> ==21263== Address 0x2FFF204 is not stack'd, malloc'd or (recently) free'd
> ==21263==
> ==21263== Process terminating with default action of signal 11
> (SIGSEGV): dumping core
> ==21263== Bad permissions for mapped region at address 0x2FFF204
> ==21263== at 0x2FFF204: ???
> ==21263== by 0x8049141: test (lib540.c:123)
> ==21263== by 0x8049366: main (first.c:85)
>
> Presumably it's been #defined to something else at some stage so the
> source at multi.c line 358 isn't what it seems.

It's #defined to curl_docalloc in memdebug.h, and curl_docalloc calls the
real malloc through the function pointer Curl_cmalloc. But that valgrind
trace implies that it's the call to curl_multi_init that goes bad. Which
is odd, because it's a plain call into a libcurl export, and not even
the first one. A compiler bug sounds more and more likely; how's your
x86 assembly language? :^)

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved