[gecode-users] strange bug in propagation

[Grégoire Dooms]

Lars Otten wrote:
> Hi,
>
> On 04/16/06 14:45, Grégoire Dooms wrote:
>   
>> Here is a (small) check list for mistakes I did and which triggered
>> segfaults later :
>> [...]
>>     
>
> What helped for me when I had a similar problem (segfault with gdb pointing
> to parts of 'normal' Gecode) was checking the problem with valgrind instead [1].
>   
Absolutely. And don't forget to configure Gecode with --enable-debug to 
disable optimizations. With -O3 valgrind makes lots of false alarms.

Best,
--
Greg.