cURL / Mailing Lists / curl-library / Single Mail


Re: Mingw64 crash but VC is ok

From: Michael <>
Date: Sun, 27 Apr 2014 23:01:05 -0700 (PDT)

PS here also the build details: 05:55:02 **** Incremental Build of configuration debug for project someplane - E64 **** mingw32-make all   'Building file: ../main.cpp' 'Invoking: Cross G++ Compiler' g++ -DLIN=0 -DREF=0 -DAPL=0 -DIBM=1 -DXPLM200 -DXPLM210 -IH:\CPP-Win\FilesWin\curl-7.28.1-devel-mingw64\include -IH:\CPP-Win\FilesWin\SDL_image-1.2.12\include -IH:\CPP-Win\FilesWin\include -IH:\CPP-Win\SDK\CHeaders\XPLM -IH:\CPP-Win\FilesWin\SDL-1.2.15\include -O3 -g -Wall -c -fmessage-length=0 -MMD -MP -MF"main.d" -MT"main.d" -o "main.o" "../main.cpp" 'Finished building: ../main.cpp' ' ' 'Building target: win.xpl' 'Invoking: Cross G++ Linker' g++ -Bstatic -lcurldll -LH:\CPP-Win\FilesWin\OpenAL_1.1_SDK\libs\Win64 -L"H:\CPP-Win\FilesWin\curl-7.34.0-devel-mingw64\bin" -L"H:\CPP-Win\someplane - E64" -LH:\CPP-Win\mingw64\lib -L"H:\CPP-Win\FilesWin\curl-7.34.0-devel-mingw64\lib64" -LH:\CPP-Win\FilesWin\SDL-1.2.15\lib\x64 -LH:\CPP-Win\FilesWin\SDL_image-1.2.12\lib\x64 -LH:\CPP-Win\SDK\Libraries\Win -shared -o "win.xpl"  ./main.o   -lopenal32 -lcurldll -lSDL -lSDL_image -lXPLM_64 -lglew32s -lopengl32 -lglu32 Warning: .drectve `/DEFAULTLIB:"LIBCMT" /DEFAULTLIB:"OLDNAMES" ' unrecognized 'Finished building target: win.xpl' ' ' mingw32-make --no-print-directory post-build strip win.xpl ' '   05:55:10 Build Finished (took 7s.627ms) ________________________________ From: Daniel Stenberg <> To: Michael <>; libcurl development <> Sent: Sunday, April 27, 2014 11:36 PM Subject: Re: Mingw64 crash but VC is ok On Sat, 26 Apr 2014, Michael wrote: > my app works fine in Linux/Mac/win32 but crashes on Win8 with mingw64. Am I > doing something wrong? I get a segfault with something alike: "cannot read > memory" You need to give us lots of more info for us to be able to tell anything. What libcurl version and what libcurl options are you using? Can you show us a full (smallish) program that repeats the problem? How far does the request reach/go before the crash? CURLOPT_VERBOSE may offer some additional clues. segfault in windows? I didn't know you could get that. Can't you run the code with a debugger and see where it crashes? --   /

List admin:
Received on 2014-04-28