09-13-2011
Cannot execute binary file
Here are outputs for commands:
# uname -a
Linux 64-cncrclinrpts 2.6.38-11-generic-pae #48-Ubuntu SMP Fri Jul 29 20:51:21 UTC 2011 i686 i686 i386 GNU/Linux
# file jasperreports-server-cp-4.1.0-linux-x64-installer.run
jasperreports-server-cp-4.1.0-linux-x64-installer.run: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, stripped
# ldd -r jasperreports-server-cp-4.1.0-linux-x64-installer.run
not a dynamic executable
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I have two Solaris machines.
1. SunOS X 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Blade-1500
2. SunOS Y 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-60
I am trying to buiild a project on both these machines. The Binary output file compiled on machine 2 runs on both the machines. Where... (0 Replies)
Discussion started by: scgupta
0 Replies
2. Linux
We are getting one error when we execute the binary file below mentioned, and ownership goes to root:nobody, how to resolve this problem.
sh /home/pub/bin/awk: cannot execute binary file
:confused:
Pls help me out . (2 Replies)
Discussion started by: durgaprasadr13
2 Replies
3. Solaris
How to execute a binary file in solaris?
I used ./setup.bin . I got the error ./setup.bin not found. (4 Replies)
Discussion started by: agarwal
4 Replies
4. Shell Programming and Scripting
HI,
i am trying to execute one .bin file which is a pre-installed (not compiled by me). But I am getting the error "cannot execute binary file".I checked the permissions and everything is ok.
also I checked ldd <bin-filename> andit showed a msg "not a dynamic executable"
Can anyone help in... (4 Replies)
Discussion started by: bhag281
4 Replies
5. SuSE
When I am trying to execute a script created by Perl2exe in Linux SLES 8.1 running with virtual machine on mainframe s/390 ....I am getting
"cannot execute binary file"....
In the linux server which are not in mainframe the scripts are fine.....
Thanks for help (1 Reply)
Discussion started by: Anu10
1 Replies
6. UNIX for Dummies Questions & Answers
As root, I receive the error message, "cannot execute binary file" when running some commands such as /usr/bin/clear or /usr/sbin/brctl or /usr/sbin/lsof. The system is running RHEL5.5. File permissions are 755. noexec is NOT set on the partitions where these files live.
I've spent a... (6 Replies)
Discussion started by: SmithJ
6 Replies
7. UNIX for Dummies Questions & Answers
Grettings,
Hi and thanks for taking a look at this. I'm going to attempt to explain this the best I possible can but due to my limited knowledge of linux this may prove difficult. I have attempted to install xcrysden on cygwin following the instruction on xcrysden webpage (I attempted to link the... (2 Replies)
Discussion started by: Zbay
2 Replies
8. Shell Programming and Scripting
Hey all,
I am using Cygwin on a machine running windows 7 64bits. I am about to use the following command:
$ faToTwoBit in.fa out.2bit
In the manual on sourceforge it mentioned:
"Download blat and faToTwoBit and set the blat_bin and fatotwobit_bin entries in config.txt to the fully... (4 Replies)
Discussion started by: @man
4 Replies
9. Fedora
Hi all,
Probably somewhat of an obvous problem here but i'm no pro.
I just bought a PengPod1000 at pengpod.com
On it I have an image of Fedora 18.
I am trying to run an application I wrote for Fedora 14 32 bit desktop on this tablet. With all permissions setup using chmod but I get... (7 Replies)
Discussion started by: fedora18
7 Replies
10. Red Hat
Hi,
When i was trying to execute binary file i am getting the below " cannot execute binary file " error message."
My Unix Version is : Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Logged in as Sudo user and $PATH Value is below
... (1 Reply)
Discussion started by: Nandy
1 Replies
LDD(1) Linux Programmer's Manual LDD(1)
NAME
ldd - print shared object dependencies
SYNOPSIS
ldd [option]... file...
DESCRIPTION
ldd prints the shared objects (shared libraries) required by each program or shared object specified on the command line. An example of
its use and output is the following:
$ ldd /bin/ls
linux-vdso.so.1 (0x00007ffcc3563000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f87e5459000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007f87e5254000)
libc.so.6 => /lib64/libc.so.6 (0x00007f87e4e92000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f87e4c22000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f87e4a1e000)
/lib64/ld-linux-x86-64.so.2 (0x00005574bf12e000)
libattr.so.1 => /lib64/libattr.so.1 (0x00007f87e4817000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f87e45fa000)
In the usual case, ldd invokes the standard dynamic linker (see ld.so(8)) with the LD_TRACE_LOADED_OBJECTS environment variable set to 1.
This causes the dynamic linker to inspect the program's dynamic dependencies, and find (according to the rules described in ld.so(8)) and
load the objects that satisfy those dependencies. For each dependency, ldd displays the location of the matching object and the (hexadeci-
mal) address at which it is loaded. (The linux-vdso and ld-linux shared dependencies are special; see vdso(7) and ld.so(8).)
Security
Be aware that in some circumstances (e.g., where the program specifies an ELF interpreter other than ld-linux.so), some versions of ldd may
attempt to obtain the dependency information by attempting to directly execute the program, which may lead to the execution of whatever
code is defined in the program's ELF interpreter, and perhaps to execution of the program itself. (In glibc versions before 2.27, the
upstream ldd implementation did this for example, although most distributions provided a modified version that did not.)
Thus, you should never employ ldd on an untrusted executable, since this may result in the execution of arbitrary code. A safer alterna-
tive when dealing with untrusted executables is:
$ objdump -p /path/to/program | grep NEEDED
Note, however, that this alternative shows only the direct dependencies of the executable, while ldd shows the entire dependency tree of
the executable.
OPTIONS
--version
Print the version number of ldd.
-v, --verbose
Print all information, including, for example, symbol versioning information.
-u, --unused
Print unused direct dependencies. (Since glibc 2.3.4.)
-d, --data-relocs
Perform relocations and report any missing objects (ELF only).
-r, --function-relocs
Perform relocations for both data objects and functions, and report any missing objects or functions (ELF only).
--help Usage information.
BUGS
ldd does not work on a.out shared libraries.
ldd does not work with some extremely old a.out programs which were built before ldd support was added to the compiler releases. If you
use ldd on one of these programs, the program will attempt to run with argc = 0 and the results will be unpredictable.
SEE ALSO
pldd(1), sprof(1), ld.so(8), ldconfig(8)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
2017-09-15 LDD(1)