| John is correct. The arguments may or may not be processed by a shell, depending on launch type, resource manager type, and target system. The arguments should never include any shell specific syntax.
Greg
On Jan 26, 2012, at 4:29 PM, John Eblen wrote: Hi Denis
Actually, I think the Run configuration output is correct. Arguments are passed verbatim to the
program and are not processed by a shell, as they would be on the command line. This behavior
may be different for older versions of Eclipse, due to some recent changes in how arguments are
processed. See bug 354893 for the details. I can't explain the Debug output, however.
Double check that you didn't run with no arguments, which is easy to do accidentally.
The "Common" tab offers options for redirecting stdin and stdout. Unfortunately, it doesn't look
like there is a way to input a file.
John
On Wed, Jan 18, 2012 at 8:32 AM, Denis Davydov <denis.davydov@xxxxxxxxxxxxxxxxxxx> wrote:
Dear Users,
I have a strange problem:
my run and debug configuration use the same executable (compiled with -g) and
run in the same folder with exactly the same arguments:
Parallel program arguments: " < in.myfile".
in main.cpp I added a line to check number of arguments:
int main(int argc, char **argv)
{
MPI_Init(&argc,&argv);
//Debug:
std::cout << "argc = " << argc;
...
}
So, Debug configuration works fine and runs as expected (argc = 1).
whereas Run configuration behaves very strange (argc = 3)!
Any ideas what might be wrong?
p/s/ Again, "Parallel program arguments" fields for both configuration are (at least visually) the same!
Kind regards,
Denis.
_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user
_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-user
|
