[gecode-users] segfault with floating-point vars

[Christian Schulte]

Hi Peter,

 

Vincent Barichard did it for us and we just helped him merge. 

 

I am quite happy because it shows that Gecode and its documentation is
accessible enough that our users can pull something like this off.

 

Christian

 

--

Christian Schulte, Professor of Computer Science, KTH,
www.ict.kth.se/~cschulte/

 

 

From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of Peter Nightingale
Sent: Thursday, May 23, 2013 12:12 PM
To: Guido Tack
Cc: users at gecode.org
Subject: Re: [gecode-users] segfault with floating-point vars

 

Thanks a lot Guido, that works fine now. 

I'm impressed that you took the plunge and implemented floating point
propagators.

Pete

On 21/05/13 18:51, Guido Tack wrote:

Yes, thanks for pointing that out.  I just fixed it in the trunk (I hope). 

 

Cheers,

Guido

 

-- 

Guido Tack

http://www.csse.monash.edu/~guidot/ <http://www.csse.monash.edu/%7Eguidot/> 

 

 

 

On 16/05/2013, at 3:23 PM, Peter Nightingale <pwn1 at st-andrews.ac.uk> wrote:





Thanks a lot Guido,

I think maybe Gecode needs to output floats rather than ints, Minizinc seems
to be complaining when parsing solution from Gecode. See output below.

pn at tamnavulin:~/chrischoi$ fzn-gecode wolf_goat_cabbage.fzn
F = 20;
I = -1;
L = -4.49423e+306;
N = -2;
R = -6.7039e+153;
k = -1;
----------
pn at tamnavulin:~/chrischoi$ mzn-gecode wolf_goat_cabbage.mzn
<standard input>:1:
 type-inst error: assignment value for `F' has invalid type-inst: expected
 `var float', actual `int'
<standard input>:2:
 type-inst error: assignment value for `I' has invalid type-inst: expected
 `var float', actual `int'
<standard input>:4:
 type-inst error: assignment value for `N' has invalid type-inst: expected
 `var float', actual `int'
<standard input>:6:
 type-inst error: assignment value for `k' has invalid type-inst: expected
 `var float', actual `int'



On 16/05/13 01:47, Guido Tack wrote:



Thanks, that was a simple bug in the FlatZinc parser, I just fixed it in the
svn.

Cheers,
Guido

On 16/05/2013, at 8:32 AM, Peter Nightingale <pwn1 at st-andrews.ac.uk> wrote:




Hi,

I get a segfault with the attached file, through mzn-gecode (with minizinc
1.6 and gecode 4.0.0 compiled from source, on Ubuntu 13.04 64-bit)

I see you have fixed a segfault for Stefano Gualandi, perhaps this file will
also work now?

Don't worry if this is not an easy fix. The problem is not that important,
and organizing CP takes higher priority!

Peter


<wolf_goat_cabbage.mzn>_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users



_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gecode.org/pipermail/users/attachments/20130523/cca5c532/attachment.html>