Using gdb to detect segmentation fault in sh?
 

I am using scientific linux. In the directory user/project/Build, after I ran 'make' to compile and link all the cpp files,I had no problems. But then, when I went to directory user/run/run.sh, which runs the project binary in user/project/Build/bin/project, I get a segmentation fault error. In the directory user/run, I enter 'gdb' in the command prompt and get the message "*** No targets specified and no makefile found. Stop."

What am I supposed to do to detect the segmentation fault?

Where program is probably /user/project/Build/bin/project and core is the core file generated when the program faulted. If you have core files disabled or limited in size, you may need to adjust ulimit settings to get a full core dump. Once in gdb, the 'bt' command will give you a stack trace to tell you the location of the crash. Post back in this thread of you need help deciphering it.

I just entered and got the message
When I then use the command prompt to go into directory and then type and then "run", I see

ulimit -c will tell you whether crashes will create core files. The core files will typically be named something like core.55909 where 55909 is the process ID. The core file will be located in the current working directory of the process that crashed, which may not be the directory that you are in.

When I then use the command prompt to go into directory

and then type I just see the output "0". Same output if I go to the directory

You have an interesting experimental approach to finding out what commands do. Boring people just use the man pages.

Try running:

so that the program will generate core files when it segfaults. On modern distros they're usually named core.XXXX where XXXX is the process ID of the crashed process. Once you have that file, you can use the commands above. Note that you may need to compile your program with special debugging options to extract meaningful information from the core dump.