Bug report #8085
A 64 bits build on Windows crash on exit
|Affected QGIS version:||master||Regression?:||No|
|Operating System:||Windows 7 64||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||16923|
I built a 64 bits version using pure native dependencies, that is everything id build with VS2010 64 bits.
Although it seams to work fine the exe crash on exit but writes a minidump file (~8 Mb).
I can upload the dump if anyone is interested.
#5 Updated by Joaquim Luis over 7 years ago
Tried to build a debug version but errors at
Linking CXX executable ..\\..\\output\\bin\\qgis.exe qtmain.lib(qtmain_win.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in main.cpp.obj Creating library qgis.lib and object qgis.exp MSVCRTD.lib(cinitexe.obj) : warning LNK4098: defaultlib 'msvcrt.lib' conflicts with use of other libs; use /NODEFAULTLIB:library ..\\..\\output\\bin\\qgis.exe : fatal error LNK1319: 1 mismatches detected LINK Pass 1 failed. with 2
#12 Updated by Matthias Kuhn over 7 years ago
I just realized, that I am not even able to extract a backtrace from the dump file without the matching binaries. I am not even sure, that the binaries would help (I remember .pdb files being important as well but that was with another compiler setup...)The possibilities I can think of to proceed are:
- You share a backtrace, so we can try to guess where the problem source is
- You can #ifdef the offending line for your system (Windows 64 bits) if this helps in your case and your system is really the only one affected
Sorry for the inconvenience.
#13 Updated by Joaquim Luis over 7 years ago
I have some experience with VS debugging but never with a dump file so I don't really know how it would work. I'm afraid that in order it work elsewhere I would have to make a copy of everything, including all the DLLs dependencies.
Sorry, I don't know either what is a backtrace. How would I produce one?
The #ifdef solution should be trivial to implement and will likely solve the problem for me, but there was another user -- Gerhard Spieles -- that reported the same problem in this thread. I didn't quite get if he had also built it's own binaries (64 bits?) or not.
Gerhard, if you are following this, can you please elaborate more about your setup?
#15 Updated by Joaquim Luis over 7 years ago
Things are getting better. With that condition it now exits cleanly but your question makes me think there is something I'm not doing write with my build. Basically what I'm doing is to include a CmakeUser.cmake file with path definitions and than run cmake & nmake. However, afaik only grass and postgres are not used here. For example, I can see in the CMakeCache.txt a line with
so doesn't that mean I am compiling with python (and wouldn't it error if I was not?)
#16 Updated by Matthias Kuhn over 7 years ago
- Status changed from Open to Closed
Closing as the original issue is solved.
It would not complain if you have no python support (to test, try to open the python console from the menu, if it does not open you have no python support)
Sorry, I can't solve the problems you just outlined.
I don't know if you are subscribed to the qgis developer mailing list. There was a request to get insight into your setup  I'm sure if you share your experiences, others will jump in and happily help you to solve the remaining problems.