LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Prabhanjan Kambadur (pkambadu_at_[hidden])
Date: 2004-08-31 01:29:22


Hi,

Sorry for the late reply. I tried replicating the issue, but could not.
Could you do a couple of things for me:

1. Could you send me the config logs for the build

2. Were you able to run any other LAM executables such as lamboot or
mpirun. Could you try running a simple hello world program and let me know
whether you see similar results.

Anju

On Thu, 26 Aug 2004, Mark wrote:

> I sent this to the developers' list, but perhaps this list is more
> appropriate for this issue.
>
>
>
> I built lam-7.1b16 on Cygwin 1.5.10 Windows XP SP 1, and when I type in
> laminfo at the prompt the cursor returns without printing any information,
> and I get the following message when I try to run hello:
>
>
>
> xxxx_at_xxxxx /mpi/lam-7.1b16/examples/hello
>
> $ mpirun C hello
>
> ----------------------------------------------------------------------------
> -
>
> It seems that [at least] one of the processes that was started with
>
> mpirun did not invoke MPI_INIT before quitting (it is possible that
>
> more than one process did not invoke MPI_INIT -- mpirun was only
>
> notified of the first one, which was on node n0).
>
>
>
> mpirun can *only* be used with MPI programs (i.e., programs that
>
> invoke MPI_INIT and MPI_FINALIZE). You can use the "lamexec" program
>
> to run non-MPI programs over the lambooted nodes.
>
> ----------------------------------------------------------------------------
> -
>
>
>
>
>
>
>
> When I debugged laminfo, I got the following:
>
>
>
>
>
>
>
> $ gdb laminfo
>
> GNU gdb 2003-09-20-cvs (cygwin-special)
>
> Copyright 2003 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 "i686-pc-cygwin"...
>
> (gdb) break 136
>
> Breakpoint 1 at 0x4010b8: file laminfo.cc, line 136.
>
> (gdb) run
>
> Starting program: /usr/local/bin/laminfo.exe
>
>
>
> Program received signal SIGSEGV, Segmentation fault.
>
> 0x6101fd44 in dlfork () from /usr/bin/cygwin1.dll
>
> (gdb)
>
>
>
>
>
>
>
> Does anyone have any insight into this problem?
>
>
>
> Thanks,
>
>
>
> Mark
>
>
>
>
>
>