Re: "init.c: No such file or directory."

On May 28, 3:25 am, Louis Krupp <lkr...@xxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Jane Smith wrote:
Hi, I am using PGI fortran with MPI (mpif90), and when I compiled and
ran my program, I got the segementation fault error. (As a matter of
fact,
it did not execute the first executable statement in my program, which
was
printning 'hello world'.)

I ran the program with a debugging option (gdb) and I got the
following messages.
-------------------------------------------------------------------------------
GNU gdb Red Hat Linux (5.2.1-4)
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 "i386-redhat-linux"...
Breakpoint 1 at 0x81bbfe6

Program received signal SIGSEGV, Segmentation fault.
0x40000a50 in .BSS1 ()
(gdb) list
1 init.c: No such file or directory.
in init.c

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

So I am not really understanding why my program
has anything to do with 'init.c' (I don't actually know what it is).
Does anybody know what these messages imply?

Another thought: Your debugger is a few years old (2002). How old is
the rest of your environment -- Fortran compiler, library, etc? Could
you update to something newer? There's nothing more frustrating than
trying to work around a problem that's been fixed.

Louis

Thank you so much for your invaluable advice. I am now trying
tailoring the program from the failing version.
As for the system, I am using the cluster system set up by the
department, so I don't have much discretion over it.
But, I would have nothing to lose by asking the IT staff to update
it :).

.

Relevant Pages

  • Re: chmod 111
    ... you can execute binaries even if the read permission is not ... Note that I said "binaries". ... GNU gdb 6.4-debian ...
    (Linux-Kernel)
  • Re: metapost or something? Coordinate system - transformation with cosine...
    ... types or functions declared in in other header files, ... Program received signal EXC_BAD_ACCESS, Could not access memory. ... tried to execute `3dldf'? ...
    (comp.text.tex)
  • Re: "init.c: No such file or directory."
    ... it did not execute the first executable statement in my program, ... GNU gdb Red Hat Linux ... then you may have a compiler installation problem. ... There might be arrays ...
    (comp.lang.fortran)
  • Re: sigsuspend() and ptrace()
    ... >>My program uses gdb to attach to a process and make it execute a specific ... >>function thanks to the gdb 'call' command. ... > the SIGSTOP even though there is no handler. ... what's expected is that sigsuspend() shouldn't ...
    (Linux-Kernel)
  • [UNIX] Progress Database Local Buffer Overflow
    ... # gdb /usr/dlc/bin/_mpros core ... Segmentation fault. ... Reading symbols from /lib/libm.so.6...done. ... There is absolutely no warranty for GDB. ...
    (Securiteam)