Hi Koen,
> The error only occurs when running in Debug mode. In Release mode,
> everything works fine, suggesting a memory initialization problem.
This is a known feature of Windows: libraries compiled in release
and debug mode are not binary compatible.
Under Linux I check with valgrind all the time, therefore it is almost
certain that the Windows debug/release mix is the only problem.
> I'm unable to debug the problem myself or get more details, as I can't
> get the library …
[View More]to compile with debugging information in it (Is there an
> easy way to do this with the Scons build system? I haven't used Scons
> before.)
The *one* script to change is
libtbx/SConscript
Currently, in the
if (sys.platform == "win32"):
...
if (env_etc.compiler == "win32_cl"):
branch you'll find:
if (libtbx.env.build_options.debug_symbols):
raise RuntimeError("Debug build not supported.")
This is the place to start.
On Unix platforms it simply works like this:
if (libtbx.env.build_options.debug_symbols):
opts.insert(0, "-g")
I forgot the details of why it is more complicated under Windows.
I vaguely recall that there were issues linking with the correct
runtime libraries, in particular linking with the correct Python
runtime.
Idea: replace the RuntimeError above with opts.insert(0, "???")
and initialize a new build directory with
libtbx\configure.py --build-boost-python-extensions=False --build=debug
Since you are not building Python extensions, the Python runtime library
problem goes away.
Ralf
[View Less]
Hi,
I'm currently in the process of writing some texture
analysis/visualization software (XRD pole figures, EBSD) and would like
to use cctbx as a basis for the crystallography calculations, as I don't
want to reinvent the wheel.
Development is in C++ on Windows, and trying one of the examples from
the code, I end up being able to crash the program, when running:
space_group_type sg_type("C 2");
This occurs using the latest release and still happens in the
(unreleased) code from 13th …
[View More]of April, both times, I compiled the library
from source, using Visual Studio 2005 and 2008. It looks to me that the
problem is situated in the Hall symbol part of the space group (those
structures are indicated as bad_ptr in the debugger, when crashing)
The error only occurs when running in Debug mode. In Release mode,
everything works fine, suggesting a memory initialization problem.
I'm unable to debug the problem myself or get more details, as I can't
get the library to compile with debugging information in it (Is there an
easy way to do this with the Scons build system? I haven't used Scons
before.)
thanks,
Koen De Keyser
--
ir. Koen De Keyser
Solid State Sciences
Ghent University
Krijgslaan 281, S1
9000 Gent, Belgium
Tel: +32 9 264 43 54
Fax: +32 9 264 49 96
Koen.DeKeyser(a)UGent.be
[View Less]