You are not logged in.
I'm new to Arch, coming from Ubuntu. I have ran into a couple applications which worked without issue on Ubuntu and fail on Arch. Is there any general advice for getting these applications to work? The application I'm most keen on getting working is Magma CAS. It gives a segmentation fault when I try to run the executable.
What I've tried:
Reinstalling.
Enabling Multilib, installing lib32-glibc and upgrading my system through pacman, then rebooting. (The executable is 64-bit, but there was a helper script on their website which was for 32-bit machines, so I thought it was worth a shot.)
Reinstalling again.
Debugging with gdb, which returns only
Program received signal SIGSEGV, Segmentation fault.
0xffffffffff600400 in ?? ()I've contacted the developers as well, but I was hoping getting a program that works on Ubuntu to work on Arch might qualify as a newbie question.
Thank you.
Last edited by junkhook9000 (2018-06-07 21:11:36)
Offline
Welcome to the arch linux forums junkhook9000. Arch_User_Repository https://aur.archlinux.org/packages/magma/
Offline
Welcome to the arch linux forums junkhook9000. Arch_User_Repository https://aur.archlinux.org/packages/magma/
Thank you! And thanks for the quick reply. It's a different software, see the link in the question.
Last edited by junkhook9000 (2018-06-07 17:38:17)
Offline
You cannot call a longer backtrace in gdb?
Is the binary statically or dynamically linked?
ldd it for details if dynamically linked.
Offline
@seth there are different builds of it http://magma.maths.usyd.edu.au/magma/do … _64-linux/
Offline
And all require some sort of account for downloading ... ;-)
Offline
You cannot call a longer backtrace in gdb?
Is the binary statically or dynamically linked?
ldd it for details if dynamically linked.
I can get a longer backtrace but it seems equally useless. Here is what I could get. I'm not familiar with gdb so maybe I'm missing something, but I can't access any of the memory addresses:
(gdb) run
Starting program: /usr/local/magma/magma.exe
Program received signal SIGSEGV, Segmentation fault.
0xffffffffff600400 in ?? ()
(gdb) bt
#0 0xffffffffff600400 in ?? ()
#1 0x0000000001d0d20d in ?? ()
#2 0x0000000000eaee4b in ?? ()
#3 0x0000000000eb2d64 in ?? ()
#4 0x0000000001ccf4fb in ?? ()
#5 0x0000000000400429 in ?? ()
#6 0x00007fffffffe498 in ?? ()
#7 0x0000000000000000 in ?? ()And yes unfortunately an account is needed to download the software.
The binary is statically linked, ldd says "not a dynamic executable".
file /usr/local/magma/magma.exe
/usr/local/magma/magma.exe: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18, BuildID[sha1]=7edcf4395cb59620f8095f687aeadd5fcbcc2e68, strippedOffline
If it's a statically linked executable you shouldn't need multilib at all... especially because it's an "ELF 64-bit LSB executable".
Do any of their other downloads work? They seem to build both static and dynamic versions, with several CPU optimizations plus a generic version...
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
If it's a statically linked executable you shouldn't need multilib at all... especially because it's an "ELF 64-bit LSB executable".
Do any of their other downloads work? They seem to build both static and dynamic versions, with several CPU optimizations plus a generic version...
I didn't see the dynamically linked versions, thank you for pointing that out. I was able to get the AVX dynamically linked version working. I was originally using the static linked AVX version, and I had tried the intel static linked version as well, both giving seg faults.
Anyway, I guess it's still a mystery why the other versions don't work on Arch when they do work on Ubuntu, but I'll mark this solved. Thank you everyone for your help.
Offline
"Since V2.20-3, the default executable is statically linked, since that is more likely to work by default (dynamically linked versions are available by clicking on "Show advanced downloads..." below)."
They should probably re-evaluate their position. ![]()
...
Anyway I guess this is a useful data point you can use to help them figure out what the issue is.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline