On Thursday, 14 January 2021 10:30:33 PM AEDT Andrew Greig via luv-main wrote:
I took a guess on the syntax alg@andrewg:~$ sudo strace ramme -v
Why did you use sudo? You run strace with the same privs as the program normally has, does ramme normally run as root?
And I got a mountain of output, the last few lines of which are here:
madvise(0x37db42585000, 1048576, MADV_DONTNEED) = 0 madvise(0x37db42599000, 4096, MADV_DONTNEED) = 0 madvise(0x37db42599000, 4096, MADV_DONTNEED) = 0 futex(0x7f75956a2f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0 futex(0x7f75956a2f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0 getrandom("\xef", 1, GRND_NONBLOCK) = 1 stat("/etc/gnutls/config", 0x7ffdb8f5b6d0) = -1 ENOENT (No such file or directory) statfs("/sys/fs/selinux", 0x7ffdb8f5b6c0) = -1 ENOENT (No such file or directory) statfs("/selinux", 0x7ffdb8f5b6c0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/proc/filesystems", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 read(3, "nodev\tsysfs\nnodev\ttmpfs\nnodev\tbd"..., 1024) = 367 read(3, "", 1024) = 0 close(3) = 0 access("/etc/selinux/config", F_OK) = -1 ENOENT (No such file or directory) --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0xe6e0c0} --- +++ killed by SIGSEGV (core dumped) +++ Segmentation fault
If the whole output is needed I will output to a text file and stuff it in Google drive and send a link
That's strange. Please try gdb. # run gdb on the executable gdb /usr/bin/ramme # gdb run command with ramme parameters r -v -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/