Executable does not execute

Executable does not execute

Post by Ingolf Markh » Tue, 15 Sep 1998 04:00:00



Hi!

I have a strange problem with an application called eclipse (a PROLOG
system): When I try to run it, the only message I get is: "No such file
or directory":

-----------------------------------------------------------------------------

/usr/local/software/eclipse/3.7.1/bin/i386_linux

total 1062
drwxr-xr-x   2 software software     1024 Mar 24 17:10 ./
drwxr-xr-x   5 software software     1024 Feb 26 21:36 ../
-rwxr-xr-x   1 software software      380 Mar 24 17:10 eclipse*
-rwxr-xr-x   1 software software   938794 Mar 20 17:47 eclipse.exec*
-rwxr-xr-x   1 software software      295 Mar 24 16:49 eclipse.orig*
-rwxr-xr-x   1 software software   138079 Mar 20 17:48 nsrv*

./eclipse: /usr/local/software/eclipse/3.7.1/bin/i386_linux/eclipse.exec: No such file or directory
./eclipse: /usr/local/software/eclipse/3.7.1/bin/i386_linux/eclipse.exec: No such file or directory

bash: ./eclipse.exec: No such file or directory

eclipse.exec: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked, not stripped
-----------------------------------------------------------------------------

It seems that ECLiPSe is trying to access a file that does not exist
on the expected place. But I have no idea which file it could be or
where it is expected by ECLiPSe.

BTW: The same software runs fine on SunOS 4.x and Solaris.

Any pointers to solve this problem?

I'd be pleased if zou could hints to me by email.

Regards,
Ingolf.

 
 
 

Executable does not execute

Post by Tom Westbroo » Thu, 17 Sep 1998 04:00:00


You might try using ldd to see if you're missing any libraries the
executable needs. Like 'ldd eclipse.exec'. If you are missing lib's make
sure the dir with the libs in it is listed in /etc/ld.so.conf & run
ldconfig after you've added it.

--
 Tom Westbrook                  
 Minneapolis, MN USA            


 
 
 

1. Executable is not executable

Hello guys,

I am having a problem with a executable I made, that the system refuses to, ehm,
execute. And it's not the simple 'execute bit not set'.

I build all my libraries in two versions, static (.a) and dynamic (.so).
The version of my executable that links the .so version works without a glitch.
When I build the statically linked version, the result is as follows:

pluto_hagen% ls -al ./TestProg
-rwxr-xr-x    1 hagen    users    11102630 Apr 29 09:12 ./TestProg

pluto_hagen% file ./TestProg
./TestProg: ELF 64-bit LSB executable, Alpha (unofficial), version 1,
dynamically linked (uses shared libs), not stripped

So far, so good. Looks like TestProg should work.

pluto_hagen% ./TestProg
./TestProg: Command not found.

Oops. Further examination of the executable yields:

pluto_hagen% ldd ./TestProg
/usr/bin/ldd: ./TestProg: No such file or directory

pluto_hagen% strace ./TestProg
execve("./TestProg", ["./TestProg"], [/* 60 vars */]) = 0
strace: exec: No such file or directory

pluto_hagen% gdb ./TestProg
GNU gdb Red Hat Linux (5.2-2)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "alpha-redhat-linux"...
(gdb) run
Starting program: /tmp/TestProg
~hagen/.cshrc: running!
/tmp/TestProg: Command not found.

Program exited with code 01.
You can't do that without a process to debug.
(gdb) quit

pluto_hagen% nm ./TestProg
000000012027b140 r a1
000000012027b148 r a2
0000000120272990 r aa
0000000120301e20 d aatEchoPara
00000001201be590 T abort
0000000000000000 a *ABS*
0000000000000000 a *ABS*
...
lots and lots more symbols, no problem.

So, I am stumped. nm seems to be the only tool that likes my executable. Can
anybody give me a hint how to examine this further? Or even had this problem
before, and solved it?

Any help very much appreciated.

Ulrich

2. vi (elvis) starts editing from the middle of xterm.

3. executable won't execute

4. NCD NC 400

5. Can't execute files that are executable

6. ldopen and object files

7. can't execute an executable file.....

8. Screen blanker...how to turn off?

9. executing missing executable

10. using popen to execute and feed input to set of executable files

11. /usr/sbin/pppd does not exist or is not executable

12. gdb: core file not in executable format: File format not recognized

13. /bsd is executable or not (to chmod or not)?