GDB exec错误：没有这样的文件或目录

Question

I have an executable, which I can read symbols from (so it seems.) My problem is this: when it comes time to run, I get the following error:

(gdb) run Starting program: /home/usr/src/etcetera/etcetera/bin/theExecutable.exe Cannot exec -c exec /home/usr/src/etcetera/etcetera/bin/theExecutable.exe. Error: No such file or directory During startup program exited with code 127

obviously, I have edited the directories here. I searched how to fix this on SO, and tried some of the following solutions:

gdb cannot see source file

GDB can't find source file

gdb can not load source file?

got onto this link:

https://sourceware.org/gdb/download/onlinedocs/gdb/Source-Path.html#Source-Path

and am trying to change the source file directory. (The source files are not in the same location as the executable, but instead are spread over a range of different places.) Unless I am mistaken, the way of doing this is to go:

(gdb) directory /home/usr/src/etcetera/etcetera/rootDirectoryForSourcefiles

and have the GDB search this directory. I have even tried changing directory into the source directory, and then running but still, it wants to try where the executable lives.

Am I completely missing the mark here in an obvious way, or is this likely to be quite obscure?

Note if you wish to downvote this question, I would appreciate an explanation as to why, so I can improve for the future

Thanks

Answer 1

You are barking up the wrong tree. You problem has ~nothing to do with source files, and everything to do with your executable file.

It may be related to something in your ~/.gdbinit , or your ~/.bashrc , or the way you invoked GDB.

You should start by doing a basic sanity check:

env SHELL=/bin/sh gdb -nx /bin/date
(gdb) run

If that doesn't work, your GDB installation is screwed up.

If that does work, one of the three things I mentioned above is very likely the cause of your troubles.

Answer 2

I had this problem and it turned out that the shell wasn't set correctly in the /etc/passwd file.

To solve it, I opened the file with

sudo vipw

and added /bin/bash to the my account's data there.

Answer 3

Try to:

export SHELL=/bin/sh

before running gdb

Answer 4

I had met same problem. When my

SHELL=/usr/local/bin/tcsh

but I have only the file .cshrc , gdb reports the same error.

When I change SHELL:

setenv SHELL /bin/csh

Then everything goes fine.