The source file is attached, and compile instructions are on the first
line. The program takes input from readline(), does mpi stuff (spawn
and merge), and prints the line index and line length to the terminal.
To reproduce, compile with should_merge set to true, then paste the
contents of main.c
On Apr 3, 2008, at 5:52 PM, Will Portnoy wrote:
Do you mean that you are starting it via ./my_mpi_program?
Yes.
This is quite odd; OMPI shouldn't be interfering much in this scenario
-- our IO forwarding stuff mostly comes into play when mpirun is used.
However, I'd like to understand wha
> Do you mean that you are starting it via ./my_mpi_program?
Yes.
> Uck. :-(
Yes. :)
> What happens if you replace readline with a simple fgets() (or
> equivalent)? That is, I'm curious to see if the problem is with
> OMPI's interaction with readline or our I/O forwarding in general.
Yes, di
On Apr 1, 2008, at 2:36 PM, Will Portnoy wrote:
I am using MPI in a somewhat nontraditional fashion. My program calls
MPI_Comm_Spawn to start worker processes that are driven by my
shell-like program. My program uses readline for input, and is *not*
started by mpirun.
Do you mean that you are
I am using MPI in a somewhat nontraditional fashion. My program calls
MPI_Comm_Spawn to start worker processes that are driven by my
shell-like program. My program uses readline for input, and is *not*
started by mpirun.
I have a problem where if I paste large amounts of text to my program
in my
