[gecode-users] Bug with Tuple, Minimizescript (Restart) and several threads

[Guido Tack]

Hi,
thanks for the report.  That's indeed a bug, I found the problem but don't have a fix for it right now.  We'll fix it for the next release.

Cheers,
Guido

On 16/07/2012, at 8:30 AM, Manuel Baclet wrote:

> Hello,
> first of all, thank you for this great software tool. I think there is a bug in Gecode when using extensional constraint with tuples,  minimizescript, restart search and several threads. For example, the following program terminates most of the time with a segmentation fault. I tested this on osX and Linux:
> <test.cp>
> 
> Everything is fine when using one thread or using bab search and i don't think that the problem occurs when using DFA or regular expressions instead of tuples.
> 
> On Linux, gdb says:
> [New Thread 0xb62b6b40 (LWP 7988)]
> [New Thread 0xb5ab5b40 (LWP 7989)]
> [New Thread 0xb52b4b40 (LWP 7990)]
> [New Thread 0xb4ab3b40 (LWP 7991)]
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb62b6b40 (LWP 7988)]
> 0xb7aacf95 in Gecode::Int::Extensional::Base<Gecode::Int::BoolView, true>::valid (this=0x806f030, t=0x11, dom=0x806e038)
>    at ./gecode/int/extensional/base.hpp:131
> 131	      if (!dom[i].get(static_cast<unsigned int>(t[i]-ts()->min)))
> 
> Regards,
> Manuel
> 
> _______________________________________________
> Gecode users mailing list
> users at gecode.org
> https://www.gecode.org/mailman/listinfo/gecode-users