Problem solved ... Apparently Windows release wasn't happy with my vector <string> returned from a static function. Why everyone else could take it? No idea.
If anyone is curious about the fix: https://github.com/dfelinto/blender/commit/181e780aa84122db540130e4cfbdf3240cf010d9 Jurgen, the new libs seem fine, no need for rebuilds. Thanks, Dalai -- blendernetwork.org/member/dalai-felinto www.dalaifelinto.com 2013/6/6 Dalai Felinto <[email protected]>: > Update on windows bug: > > The crash is actually in the new code inside > imb_exr_get_multiView_id() when I access the (*views).end() or even > simply *i. (this is part of a string const_iterator) > > I tried different things (e.g., replacing the StringVector in the code > by std::vector <std::string>; to take the StringVector functions and > move it to outside the extern "C" part) ... nothing works. > > Or better, nothing make it work in release, but nothing affects debug > (which still works like a charm). > So ... do we really need to support Windows? *cough* > > As soon as I find a solution I'm seriously considering to #ifdef WIN > and ifndef DEBUG and hide whatever hack we need there. And debugging > with printfs is soooo fun. > -- > Dalai > > > 2013/6/5 Dalai Felinto <[email protected]>: >>> have you tried to build a "RelWithDebInfo" Build of OpenEXR? >> >> I tried, but if I build Blender as debug using the openexr build as >> Release with Debug Info it crashes at launch: >> http://www.pasteall.org/42864 >> >> I've been debugging via a computer I have access via RDC so it's >> really annoying btw. >> >> Leaving this RelWithDebInfo aside and focusing on the original problem >> (library working in debug but not in release), does any one have a >> clue on what can cause that? Namespace conflict? ...? ...? >> >> -- >> Dalai >> >> 2013/6/5 Jürgen Herrmann <[email protected]>: >>> Hi Dalai, >>> >>> have you tried to build a "RelWithDebInfo" Build of OpenEXR? >>> This could help to track down the Error if the Debug Lib doesn't help. >>> >>> /Jürgen >>> >>> Am 05. Juni 2013 um 10:40 schrieb Dalai Felinto <[email protected]>: >>> >>>> I found where the crash is (still no idea why it's crashing): >>>> >>>> ################# >>>> openexr_api.cpp::imb_load_openexr (...) >>>> (...) >>>> >>>> Mem_IStream *membuf = new Mem_IStream(mem, size); >>>> ################# >>>> >>>> To get there I had to build a debug build and replace the linking to: >>>> >>>> \lib\windows\openexr\lib\IlmImf.lib >>>> instead of: >>>> \lib\windows\openexr\lib\IlmImf_d.lib >>>> >>>> And it consistently breaks on Release for windows and 64, but not for >>>> Debug. >>>> Any clues on how to debug this? >>>> >>>> -- >>>> Dalai >>>> >>>> -- >>>> blendernetwork.org/member/dalai-felinto >>>> www.dalaifelinto.com >>>> >>>> >>>> 2013/6/3 Jürgen Herrmann <[email protected]>: >>>> > Hi Dalai, >>>> > >>>> > I can recompile the libs tomorrow. I'll contact you when I am done. >>>> > I doubt that this will change anything though. The header that was >>>> > missing wasn't installed by the CMake build routine it was not missing >>>> > at compile time. >>>> > It was just omitted by the install script. >>>> > But nevertheless I'll try to recompile them for you. >>>> > Otherwise we should try to report a bug to the OpenEXR devs. It could be >>>> > an error in the libs. >>>> > >>>> > /Jürgen >>>> > >>>> > Am 03.06.2013 um 20:58 schrieb Dalai Felinto <[email protected]>: >>>> > >>>> >> Hi again, >>>> >> >>>> >> The new OIIO libraries don't make any difference. OIIO depends on >>>> >> OpenEXR and not the other way around. So although that could I can't >>>> >> see how they would change things. >>>> >> >>>> >> I remember when you first uploaded the libraries you forgot a header >>>> >> file (which I'm using in the code). I wonder if it's related and the >>>> >> first "release" build is buggy. The ideal would be to rebuild OpenEXR >>>> >> for release and hope it fixes the problem. >>>> >> >>>> >> If you don't want to commit the libs without knowing they will fix the >>>> >> problem you can put them on blender.org ftp incoming folder. (or poke >>>> >> me on IRC and we can find a solution). >>>> >> >>>> >> (or checkout the svn code for multiview, it should be easy to >>>> >> reproduce the problem in your windows station) >>>> >> >>>> >> Thanks, >>>> >> Dalai >>>> >> >>>> >> >>>> >> -- >>>> >> blendernetwork.org/member/dalai-felinto >>>> >> www.dalaifelinto.com >>>> >> >>>> >> >>>> >> 2013/6/2 Jürgen Herrmann <[email protected]>: >>>> >>> Hi Dalai, >>>> >>> >>>> >>> Thomas Dinges asked me to downgrade OIIO to 1.1.11 just today. >>>> >>> Please try to do a SVN update on your libs and compile again using >>>> >>> these. >>>> >>> These problems are strange... >>>> >>> I will have a closer look on this tomorrow. >>>> >>> >>>> >>> /Jürgen >>>> >>> >>>> >>> Am 02.06.2013 um 20:16 schrieb Dalai Felinto <[email protected]>: >>>> >>> >>>> >>>> Hi Jurgen, >>>> >>>> I think the problem is the release library. >>>> >>>> >>>> >>>> Even with cmake+msvc the exr sample image fails when I build release. >>>> >>>> And I just tested with the 1.2 oiio libraries and I still get the same >>>> >>>> error with scons+msvc debug. >>>> >>>> >>>> >>>> Remember that you forgot to include a header in your first commit of >>>> >>>> the library? I wonder if that was somehow also missing when you built >>>> >>>> it. I don't know. >>>> >>>> >>>> >>>> -- >>>> >>>> Dalai >>>> >> _______________________________________________ >>>> >> Bf-committers mailing list >>>> >> [email protected] >>>> >> http://lists.blender.org/mailman/listinfo/bf-committers >>>> > _______________________________________________ >>>> > Bf-committers mailing list >>>> > [email protected] >>>> > http://lists.blender.org/mailman/listinfo/bf-committers >>>> _______________________________________________ >>>> Bf-committers mailing list >>>> [email protected] >>>> http://lists.blender.org/mailman/listinfo/bf-committers >>> _______________________________________________ >>> Bf-committers mailing list >>> [email protected] >>> http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
