Hi J-S,
Hmm, that's interesting, never used that combination. Do you know how
I enable Debug info for Release mode?
When building OSG, after generating the project files with CMake, if
you open the solution file you'll see "RelWithDebInfo" as one of the
available configurations.
For other projects, you can do it manually by enabling debug symbols
in the C/C++ section of the project options, and enabling debugging in
the Linker section, for a release build.
I should note that you'll probably get weird results from breakpoints
and checking the values of variables (because of compiler optimization
in release mode). You can disable optimization but the crash might
only happen when optimization is at a certain setting... So it's not
perfect but might help you get closer to the bug.
Ok, thanks for this info. I know about the optimizations... I will look
into it.
When something crashes in release but not in debug, it's often an
uninitialized variable or something like that. Since the debug builds
generally protect you more (initializing variables to known values for
example) this sometimes hides bugs that only happen in release.
Yup, indeed, a lot of times (always?) the compiler initializes
parameters to 0 in debug mode.
I've seen, on another machine on which it crashed in both debug and
release mode, that it has to do with the mutex and such. I don't recall
the actual location but it seemed to me that the OSG thread
functionality and the SDL functionality were 'fighting' somehow...
In the mean time I've tried with that latest version SDL 1.2.14 but
still the same result.
cheers
Raymond
Hope this helps,
J-S
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
