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

outputJSON with a large number of variables causes segfault #856

Open
CervEdin opened this issue Oct 15, 2024 · 2 comments
Open

outputJSON with a large number of variables causes segfault #856

CervEdin opened this issue Oct 15, 2024 · 2 comments
Labels

Comments

@CervEdin
Copy link

Using a lot of variables with the outputJSON seems to create a segfault in 2.8.7

In 2.8.5 I instead get

Error: syntax error, unexpected '{', expecting FZ_SOLVE in line no. 4219
=====ERROR=====
array[1..100] of var int: a00;
array[1..100] of var int: a01;
array[1..100] of var int: a02;
array[1..100] of var int: a03;
array[1..100] of var int: a04;
array[1..100] of var int: a05;
array[1..100] of var int: a06;
array[1..100] of var int: a07;
array[1..100] of var int: a08;
array[1..100] of var int: a09;
array[1..100] of var int: a10;

array[1..100] of var int: a11;
array[1..100] of var int: a12;
array[1..100] of var int: a13;
array[1..100] of var int: a14;
array[1..100] of var int: a15;
array[1..100] of var int: a16;
array[1..100] of var int: a17;
array[1..100] of var int: a18;
array[1..100] of var int: a19;
array[1..100] of var int: a20;

array[1..100] of var int: a21;
array[1..100] of var int: a22;
array[1..100] of var int: a23;
array[1..100] of var int: a24;
array[1..100] of var int: a25;
array[1..100] of var int: a26;
array[1..100] of var int: a27;
array[1..100] of var int: a28;
array[1..100] of var int: a29;
array[1..100] of var int: a30;

array[1..100] of var int: a31;
array[1..100] of var int: a32;
array[1..100] of var int: a33;
array[1..100] of var int: a34;
array[1..100] of var int: a35;
array[1..100] of var int: a36;
array[1..100] of var int: a37;
array[1..100] of var int: a38;
array[1..100] of var int: a39;
array[1..100] of var int: a40;

array[1..100] of var int: a41;
array[1..100] of var int: a42;
array[1..100] of var int: a43;
array[1..100] of var int: a44;
array[1..100] of var int: a45;
array[1..100] of var int: a46;
array[1..100] of var int: a47;
array[1..100] of var int: a48;
array[1..100] of var int: a49;
array[1..100] of var int: a50;

array[1..100] of var int: a51;
array[1..100] of var int: a52;
array[1..100] of var int: a53;
array[1..100] of var int: a54;
array[1..100] of var int: a55;
array[1..100] of var int: a56;
array[1..100] of var int: a57;
array[1..100] of var int: a58;
array[1..100] of var int: a59;
array[1..100] of var int: a60;

array[1..100] of var int: a61;
array[1..100] of var int: a62;
array[1..100] of var int: a63;
array[1..100] of var int: a64;
array[1..100] of var int: a65;
array[1..100] of var int: a66;
array[1..100] of var int: a67;
array[1..100] of var int: a68;
array[1..100] of var int: a69;
array[1..100] of var int: a70;

array[1..100] of var int: a71;
array[1..100] of var int: a72;
array[1..100] of var int: a73;
array[1..100] of var int: a74;
array[1..100] of var int: a75;
array[1..100] of var int: a76;
array[1..100] of var int: a77;
array[1..100] of var int: a78;
array[1..100] of var int: a79;
array[1..100] of var int: a80;

array[1..100] of var int: a81;
array[1..100] of var int: a82;
array[1..100] of var int: a83;
array[1..100] of var int: a84;
array[1..100] of var int: a85;
array[1..100] of var int: a86;
array[1..100] of var int: a87;
array[1..100] of var int: a88;
array[1..100] of var int: a89;
array[1..100] of var int: a90;

array[1..100] of var int: a91;
array[1..100] of var int: a92;
array[1..100] of var int: a93;
array[1..100] of var int: a94;
array[1..100] of var int: a95;
array[1..100] of var int: a96;
array[1..100] of var int: a97;
array[1..100] of var int: a98;
array[1..100] of var int: a99;
array[1..100] of var int: a100;

output outputJSON();
@cyderize cyderize added the bug label Oct 16, 2024
guidotack pushed a commit that referenced this issue Oct 29, 2024
@cyderize
Copy link
Member

We believe we've now fixed what was causing this problem in develop.

@CervEdin it would be great if you could try the edge build and confirm that it actually works now, since on my machine the example provided never seemed to actually segfault.

Thanks!

@CervEdin
Copy link
Author

@cyderize oooh, I never noticed there was an edge build published here, I will try using edge on snap and see if I can repro the error + fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants