Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[2.8.0] Negated N-ary forall constraint with concatenation causes segmentation fault #754

Closed
IgnaceBleukx opened this issue Nov 24, 2023 · 1 comment
Assignees
Labels
bug resolved Issue is resolved and the feature or fix will be part of next release

Comments

@IgnaceBleukx
Copy link

Hi,

I am using MiniZinc to solve the following model:

var bool: a;
var bool: b;
var bool: c;
var bool: d;

constraint not(forall([a \/ b] ++ [c \/ d]));

When compiling, this results in a segmentation fault:

>>MiniZinc error: Memory violation detected (segmentation fault). This is a bug. Please file a bug report using the MiniZinc bug tracker. Process finished with non-zero exit code 6. Finished in 231msec.

I know this is quite strange use of the forall and concatenation operators, but I would still expect this model to work as it is within spec?

When removing the concatenation and replacing it with a single list, or removing the negation, the model works fine.

Kind regards,
Ignace

@cyderize cyderize added the bug label Nov 24, 2023
@Dekker1 Dekker1 self-assigned this Nov 26, 2023
@Dekker1 Dekker1 added the resolved Issue is resolved and the feature or fix will be part of next release label Nov 26, 2023
@cyderize
Copy link
Member

This should now be fixed in 2.8.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug resolved Issue is resolved and the feature or fix will be part of next release
Projects
None yet
Development

No branches or pull requests

3 participants