Re: Recap: Cepstral Swift and Debian Stretch

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

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
> Cepstral_William_x86-64-linux_6.2.3.873.tar.gz
> 
> 
> It was downloaded with wget from a link given to me from support at
> cepstral.com. 
> 
> 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

  /lib64/ld-linux-x86-64.so.2

(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  -f 

(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
> habits.

No worries. I just re-ordered things as posting styles got too mixed
up :-)

Regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAli138QACgkQBcgs9XrR2kYNJQCeKp4Ny0SP/xBp9LOUhG/7v2L8
ygIAn04KBtt/60arZ2Uex9xqP0pt46p3
=4bcY
-END PGP SIGNATURE-

Recap: Cepstral Swift and Debian Stretch

[Chuck Hallenbeck]

Here is a summary of what we now know:

The only package in play now is
Cepstral_William_x86-64-linux_6.2.3.873.tar.gz


It was downloaded with wget from a link given to me from support at
cepstral.com. 

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

I obtained a checksum on each swift.bin, and those too were identical,
each one was this:

bf67fecfbae44e68f2c6d669fbb65512e197db87  /opt/swift/bin/swift.bin

By "identical" I mean I saved each output to a file and used diff to
compare them, no output was produced.

The hardware is a Dell Optiplex 780 with plenty of ram and CPU power,
Debian is using kernel 4.9.0, and Arch is using 4.9.11.  Swift executes
without error on Arch, but on Debian where I want to use it, it reports
a bad format for swift.bin, which ldd also describes an not an
executable ffile.

Sorry about  earlier top-posts, I'm new to the list and have bad
habits.

Chuck





-- 
When you've seen one shopping center you've seen a mall.
Willoughby Ohio
   Temperature 43°F
   Conditions Mostly Cloudy
The Moon is Waxing Crescent (5% of Full)