Re: Recap: Cepstral Swift and Debian Stretch
- Date: Tue, 28 Feb 2017 21:38:28 +0100
- From: <tomas@xxxxxxxxxx>
- Subject: Re: Recap: Cepstral Swift and Debian Stretch
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, Feb 28, 2017 at 08:30:13AM -0500, Chuck Hallenbeck wrote:
> Here is a summary of what we now know:
> The only package in play now is
> It was downloaded with wget from a link given to me from support at
> The package was downloaded to Debian Stretch on a dual boot system
> where Arch Linux is the secondary OS. It was installed on Debian, and
> after problems were discovered, was moved to Arch and installed there,
> where it ran without error.
> The output of file for the swift.bin executable was identical on b oth
> systems, and was:
> ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
> linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.9,
> not stripped, with debug_info
Since the binary is the same, the difference must be in the environment.
The first stop would be to check what's behind
(background: that's the dynamic linker. Every executable has an
"interpreter" which takes care of running it, e.g. for a shell
executable it might be /bin/sh. For ELF executables, it's ld-linux*.so,
with some variations depending on architecture). There is actually a
man page for it (man 8 ld.so)).
A second approach would be calling the program under strace and see
whether there's some usable info, like so:
strace -o <some.file.name.for.trace> -f <your.program>
(the f means "follow" across forks: thus you might call the shell wrapper
to let it do its setup).
The output is very verbose, but since the program dies quickly, you can
look at the end of the trace file for hints.
Strace records the system calls and their results.
Just ask away when stuck.
> Sorry about earlier top-posts, I'm new to the list and have bad
No worries. I just re-ordered things as posting styles got too mixed
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----