Error with tutorial

[Davide Ferrari]

Hi,

I wanted to try out SCALE-MAMBA. I followed the installation instructions with nix-shell.

When I run 

./Player.x 0 Programs/tutorial

 (or any other program) I get the following error:

ERROR: ./Player.x: line 10: 3523 Illegal instruction ./PlayerBinary.x "$@"

I do not know how to solve the problem.

If anyone could help me, it would be wonderfull

Thanks in advance.

[Kelong Cong]

Hi,

I'm not sure what went wrong there. I downloaded the github repo again,
installed it using nix and it worked.

Could you write down the exact steps you followed that led to this
error? Then I can try to spot the error.

You can also try to run
./PlayerBinary.x 0 Programs/tutorial
and see if that does anything.

Kelong

> --
> You received this message because you are subscribed to the Google
> Groups "SPDZ/SCALE-MAMBA Discussion Group" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to spdz+uns...@googlegroups.com
> <mailto:spdz+uns...@googlegroups.com>.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/spdz/16f4a421-ec73-4506-8cf5-e7bfef1b38b6n%40googlegroups.com
> <https://groups.google.com/d/msgid/spdz/16f4a421-ec73-4506-8cf5-e7bfef1b38b6n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Davide Ferrari]

Hi,

 this is the sequence of instruction, executed on a fresh installation of Ubuntu 20.04.3 LTS (Focal Fossa):

-  curl -L https://nixos.org/nix/install | sh

- . /home/dferra/.nix-profile/etc/profile.d/nix.sh

- git clone https://github.com/KULeuven-COSIC/SCALE-MAMBA

- cd SCALE-MAMBA/

- nix-shell

- cp CONFIG CONFIG.mine (in CONFIG.mine commented OSSL and set ROOT = ..)

- make progs

-  cp Auto-Test-Data/Cert-Store/* Cert-Store/

-  cp Auto-Test-Data/1/* Data/

- ./compile.sh Programs/tutorial/

- ./Player.x 0 Programs/tutorial

+ '[' '' == 1 ']'
+ ./PlayerBinary.x 0 Programs/tutorial
./Player.x: line 10: 104926 Illegal instruction     (core dumped) ./PlayerBinary.x "$@"

The same thing happens if I run PlayerBinary.x, or even SetupBinary.x.

Illegal instruction (core dumped)

I am starting to think that it is some strange incompatibility with either my hardware or OS.

[Kelong Cong]

These steps seem fine. It does seem like a hardware issue. Are you using
an Intel CPU?

Could you also try to just run gdb on PlayerBinary.x and see the
backtrace? Maybe it'll tell you exactly what went wrong.

Kelong

> <https://groups.google.com/d/msgid/spdz/16f4a421-ec73-4506-8cf5-e7bfef1b38b6n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/spdz/16f4a421-ec73-4506-8cf5-e7bfef1b38b6n%40googlegroups.com?utm_medium=email&utm_source=footer>>.

>
>
> --
> You received this message because you are subscribed to the Google
> Groups "SPDZ/SCALE-MAMBA Discussion Group" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to spdz+uns...@googlegroups.com
> <mailto:spdz+uns...@googlegroups.com>.
> To view this discussion on the web, visit

> https://groups.google.com/d/msgid/spdz/5112b4dc-6287-416c-9194-eb2d767759den%40googlegroups.com
> <https://groups.google.com/d/msgid/spdz/5112b4dc-6287-416c-9194-eb2d767759den%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Nigel Smart]

What is the CPU? Could be something to do with our use
of special instructions

Nigel

--
Nigel Smart

[Davide Ferrari]

My CPU is an Intel(R) Xeon(R) CPU E5-2640 v2 @ 2.00GHz.

With gdb on PlayerBinary.x I get:

0x0000000000420c21 in _GLOBAL__sub_I_RunTime.cpp ()
(gdb) bt
#0  0x0000000000420c21 in _GLOBAL__sub_I_RunTime.cpp ()
#1  0x000000000059c425 in __libc_csu_init ()
#2  0x00007ffff71a8c0c in __libc_start_main () from /nix/store/9df65igwjmf2wbw0gbrrgair6piqjgmi-glibc-2.31/lib/libc.so.6
#3  0x0000000000421e6a in _start () at ../sysdeps/x86_64/start.S:120

For SetupBinary.x:

Program received signal SIGILL, Illegal instruction.
0x000000000040c1da in init_secret_sharing_inner(std::istream&) ()
(gdb) bt
#0  0x000000000040c1da in init_secret_sharing_inner(std::istream&) ()
#1  0x000000000040ae0a in main ()

[Kelong Cong]

The backtrace doesn't seem to say much but your CPU is old (from 2011).

I suspect it's an issue with the nix's version of mpir. There are
similar issues here https://github.com/NixOS/nixpkgs/issues/58950

Maybe you can try this workaround?
https://github.com/NixOS/nixpkgs/issues/58950#issuecomment-819823418

Kelong

> <https://groups.google.com/d/msgid/spdz/5112b4dc-6287-416c-9194-eb2d767759den%40googlegroups.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/spdz/5112b4dc-6287-416c-9194-eb2d767759den%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> >>
> >
>
> --
> Nigel Smart
>

> --
> You received this message because you are subscribed to the Google
> Groups "SPDZ/SCALE-MAMBA Discussion Group" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to spdz+uns...@googlegroups.com
> <mailto:spdz+uns...@googlegroups.com>.
> To view this discussion on the web, visit

> https://groups.google.com/d/msgid/spdz/ac0245d9-79e0-4ae4-9b6a-e94be6f2f1afn%40googlegroups.com
> <https://groups.google.com/d/msgid/spdz/ac0245d9-79e0-4ae4-9b6a-e94be6f2f1afn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Davide Ferrari]

Hi, the CPU is indeed too old. And the workaround did not work.

Fortunately, I gained access to a machine with a more recent CPU and it works just fine.

Thanks for the help.