enhance this inquiry
edited Jul 6 "18 in ~ 8:58
10.2k99 yellow badges3636 silver badges6868 bronze title
request Jul 6 "18 in ~ 8:33
4311 silver badge44 bronze badges
include a comment |
1 answer 1
energetic earliest Votes
It seems you may be feather for:
gdb --args ./RelayD start --daemon(although you most likely want to stop --daemon if that"s optional).
You are watching: Not in executable format: file format not recognized
However, that over (shell) command is tantamount to:
gdb ./RelayD... Complied with by (on the GDB prompt):
run start --daemonNote how in both instances I to be passing the disagreements as per the script line and also how ns am passing the relative path rather of simply the surname of an executable.
There may be an additional catch here, but it"s hard to tell and you don"t explicitly point out the distro you"re on. However, it"s feasible that for your mechanism you require to enable multilib assistance <1> so that your x86-64 OS can run x86-32 binaries (that RelayD ELF file) and that you may need to install part packages you need to install in stimulate to have GDB support this scenario. The alternative could be to operation a 32-bit container (which still needs multilib, if ns am not mistaken) and inside that prepare and debug with a 32-bit GDB or use a 32-bit VM to obtain the debugging done. Yet for every I know most distros assistance the scenario of debugging a 32-bit binary top top the 64-bit host system. Therefore it"s most likely a matter of installing some extra packages.
Oh and also last however not the very least you might be missing some of the common objects (libraries) that the 32-bit executable expects. Usage readelf or ldd on your RelayD to discover out more.
See more: How Long For Joint Compound To Dry Wall Joint Compound Take To Dry?
<1> yum groupinstall "Compatibility Libraries" have to do the trick, listed multilib_policy=all is collection in your yum.conf and you"re certainly running on RHEL (or CentOS or scientific Linux) as argued by the GDB output you gave. Likewise make certain yum.conf does not save on computer exclude = *.i?86 come preclude the 32-bit packages from being considered (exactarch=1 may likewise have an adverse effect, for this reason consult man yum.conf). You can also pick and also choose your own compatibility libraries by browsing the list through yum find compat|grep ^compat-.