-
Notifications
You must be signed in to change notification settings - Fork 74
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
Segmentation fault with "minizinc" command #202
Comments
I'm afraid that the error by itself won't give us any clues unless you post the model (instance) that you are compiling. Note that |
I do not need any model instance. The segfault happens even with no arguments or simply My workaround shell script succeeds by avoiding to call the Note that the errors happens both with the Debian packaged release of MiniZinc (although mzn-gecode is missing in the Debian package, the The issue is very probably linked to the specific environment I work in (although Debian unstable is a fairly popular distribution), but I am not familiar enough with mercury or C++ to investigate this by myself. |
It's possible that some libraries have changed on Debian Unstable that mean
it's no longer compatible with the old runtime used for the minizinc
binary. There is a replacement driver (called mzn-fzn) that isn't 100%
ready for release yet but it's built by default when you build libminizinc
from sources, so that may be an alternative for you. It will replace the
minizinc binary starting with release 2.2.0.
|
Can confirm the same error with minizinc-ide v2.1.7-1 under Arch Linux. Although I'm unsure which package update caused the error. Running |
I, too, was bitten by this bug, just before the deadline of the coursera course... I wrote a shell script wrapper as a workaround:
Would it be possible to compile minizinc as a statically linked executable ? |
@edouardklein It's a shame you ran into the same problem when you where on a deadline. As said before, we intend to replace the Note that your script will actually not use any output statement from the provided MiniZinc model. Instead of using |
You should also be able to use the MiniZinc IDE for submitting your
solutions to Coursera, since it doesn't use the minizinc binary.
Cheers,
Guido
…On Mon, Mar 12, 2018 at 10:56 AM, Jip J. Dekker ***@***.***> wrote:
@edouardklein <https://github.com/edouardklein> It's a shame you ran into
the same problem when you where on a deadline. As said before, we intend to
replace the minizinc executable in the next release. The easiest solution
is still to replace minizinc with mzn-fzn
Note that your script will actually not use any output statement from the
provided MiniZinc model. Instead of using sed you would have to use
solns2out, a tool provided which will use the output model.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#202 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJ7eTKcCqyvEX4RnMja0XK2-FE2p7b17ks5tdbmdgaJpZM4SJ3Uu>
.
--
*GUIDO TACK*
Senior Lecturer
*Information Technology*
Monash University
Level 6, Room 6.40, Building H, Caulfield Campus
900 Dandenong Road
Caulfield East VIC 3145
Australia
T: +61 3 9903 1214
E: guido.tack@monash.edu
http://users.monash.edu/~guidot/
|
I also had the issue with Coursera. Coursera provides scripts that rely on
the minizinc command with various command-line parameters. This makes
tricky to design workarounds.
Le lun. 12 mars 2018 à 01:14, Guido Tack <notifications@github.com> a
écrit :
… You should also be able to use the MiniZinc IDE for submitting your
solutions to Coursera, since it doesn't use the minizinc binary.
Cheers,
Guido
On Mon, Mar 12, 2018 at 10:56 AM, Jip J. Dekker ***@***.***>
wrote:
> @edouardklein <https://github.com/edouardklein> It's a shame you ran
into
> the same problem when you where on a deadline. As said before, we intend
to
> replace the minizinc executable in the next release. The easiest solution
> is still to replace minizinc with mzn-fzn
>
> Note that your script will actually not use any output statement from the
> provided MiniZinc model. Instead of using sed you would have to use
> solns2out, a tool provided which will use the output model.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <
#202 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AJ7eTKcCqyvEX4RnMja0XK2-FE2p7b17ks5tdbmdgaJpZM4SJ3Uu
>
> .
>
--
*GUIDO TACK*
Senior Lecturer
*Information Technology*
Monash University
Level 6, Room 6.40, Building H, Caulfield Campus
900 Dandenong Road
<https://maps.google.com/?q=900+Dandenong+Road+%0D%0ACaulfield+East+VIC+3145+%0D%0AAustralia&entry=gmail&source=g>
Caulfield East VIC 3145
<https://maps.google.com/?q=900+Dandenong+Road+%0D%0ACaulfield+East+VIC+3145+%0D%0AAustralia&entry=gmail&source=g>
Australia
<https://maps.google.com/?q=900+Dandenong+Road+%0D%0ACaulfield+East+VIC+3145+%0D%0AAustralia&entry=gmail&source=g>
T: +61 3 9903 1214 <+61%203%209903%201214>
E: ***@***.***
http://users.monash.edu/~guidot/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#202 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC67Nc8jN1Wa8JP5TYMLga0bNu-YaOHuks5tdb3NgaJpZM4SJ3Uu>
.
|
The minizinc command in release 2.2.0 is a complete rewrite that hopefully fixes these problems. |
I run MiniZinc 2.1.7 on Debian Unstable. I got the following error with mzn-* commands (whichever solver is run):
Note that mzn2fzn and fzn-* commands work well. I could design a workaround by rewritting mzn-gecode as a quick & dirty bash script, but it would be better if it worked as expected :)
The text was updated successfully, but these errors were encountered: