Dear Matthias. Thank you for the reply. I did the following:
I recompiled alps using new empty build directory with "-D CMAKE_BUILD_TYPE=Debug” in the cmake command, but still gdb produces the following:
Program received signal SIGSEGV, Segmentation fault. 0x00000001000e4468 in ?? () (gdb) bt #0 0x00000001000e4468 in ?? () #1 0x00007fff5fbfbed0 in ?? () #2 0x00007fff5fbfc168 in ?? () #3 0x00007fff5fbfbed0 in ?? () #4 0x000000010004cf95 in ?? () #5 0x0000000104683cc0 in ?? () #6 0x0000000104938940 in ?? () #7 0x0000000000000000 in ?? () (gdb) quit
So no debug information. I would appreciate any information of what I could be doing wrong. Is setting the flag ""-D CMAKE_BUILD_TYPE=Debug” enough?
I have noticed that there was some effect: for example mps_optim produces a lot more on the output (I’d say due to std::count << mps.description() << std::endl; ) , so I guess some debug option is being printed but this would be triggered by passing a proper flag like “-D DEBUG” to the preprocessor, but I am hoping for “-g” for the compiler.
Best, Mateusz
On 07 Aug 2015, at 16:30, Matthias Troyer troyer@phys.ethz.ch wrote:
Yes, just switch the build mode in cmake from Release to Debug
Matthias
On 07 Aug 2015, at 07:20, Mateusz Łącki mateusz.lacki@gmail.com wrote:
Dear All, I would like to ask for some practical tips how to effectively debug alps applications:
Is there a way how to build alps with debug flags switched on?. I would appreciate an ability to use a debugger such as gdb to debug the alps applications code. Does the debugging logic depend heavily on a particular alps application (meaning is debugging modifications of mps_optim moreless equivalent to debugging dwa code)?
Can this debug mode be turned on using the cmake flags?
Best, Mateusz Łącki