CODEWITHSUNDEEP
c++windowscommand-line-argumentsmsvc12
codefox
codefox

Reputation: 31

Issues with C++ command-line arguments on Windows

I'm somehow having issues parsing command-line arguments on Windows in C++. I tried using this

int main(int argc, char **argv)
{
    std::cout << "Command-line argument count: " << argc << " \n";
    std::cout << "Arguments:\n";
    for (int i = 0; i < argc; i++)
        std::cout << "  argv[" << i << "]   "
        << argv[i] << "\n";

    return 0;
}

as well as this

int main(int argc, char *argv[])
{
    std::cout << "Command-line argument count: " << argc << " \n";
    std::cout << "Arguments:\n";
    for (int i = 0; i < argc; i++)
        std::cout << "  argv[" << i << "]   "
        << argv[i] << "\n";

    return 0;
}

The variables argc and argv seem to be somehow uninitialized. That's what launching the program returns to me:

Z:\Dev\ProcessSuspender\Debug>ProcessSuspender a
Command-line argument count: 2130558976
Arguments:
  argv[0]
  argv[1]   ╠ÉÉÉÉÉj↑h╚♂YwÞØ÷■ âe³
  argv[2]

(crash following)

I compiled it with MSVC12 using the /SUBSYSTEM:CONSOLE linker option. What could be the cause of this issue?

Upvotes: 2

Views: 2157

Answers (4)

Rufflewind
Rufflewind

Reputation: 8956

I've manually set the entry point to main. Whether I use the default project setting (_tmain) or not, the issue persists.

In general, you should not do that unless you know the consequences. The typical values of the entry point (/ENTRY) should be either:

  • [w]mainCRTStartup, which calls [w]main, or
  • [w]WinMainCRTStartup, which calls [w]WinMain, or
  • _DllMainCRTStartup, which calls DllMain.

Why is this needed? Well, the …CRTStartup-family of functions do a couple crucial things, including the initialization of:

  • the C runtime (CRT),
  • any global variables, and
  • the arguments argc and argv, as you've accidentally found out.

So for a typical program you probably want it to do its job. In the Linux world, there is an equivalent function called _start that is needed to do the same initialization tasks as well, which can be overridden with -e while linking.

The confusion here probably stems from difference in ambiguous meaning of the word "entry point": there is the meaning of "apparent entry point" from the perspective of the language (which is main and its ilk), and the meaning of the "true entry point" from the perspective of the language implementation (which is …CRTStartup or _start).

Note that using the …CRTStartup functions is not absolutely essential, as you can certainly write a program that avoids using them. It does come with a cost, however:

  • you can't use the C runtime, so you can't use most of the standard library,
  • you need to manually initialize any global variables, and
  • you need to manually obtain argc and argv using the Windows API (GetCommandLineW and CommandLineToArgvW).

Some do this to avoid dependency on the CRT, or to minimize the executable size.

Upvotes: 6

AneesAhmed777
AneesAhmed777

Reputation: 2695

Obviously, Something is wrong with the IDE or project or maybe anything else's setup on your system only. The code is perfect.

Have you tried directly and independently running your output exe, by executing it through command prompt ??

Run your exe with command prompt by supplying some arbitrary arguments, and check the output.

Upvotes: 0

GingerJack
GingerJack

Reputation: 3134

its worth to check your character set in project properties->General.

Upvotes: -1

Ganesh Kamath - &#39;Code Frenzy&#39;
Ganesh Kamath - &#39;Code Frenzy&#39;

Reputation: 5283

I tried your project on VS 2012 and it is working smoothly. I added a getchar(); command as below:

#include <iostream>

int main(int argc, char *argv[])
{
    std::cout << "Command-line argument count: " << argc << " \n";
    std::cout << "Arguments:\n";
    for (int i = 0; i < argc; i++)
        std::cout << "  argv[" << i << "]   "
        << argv[i] << "\n";
    getchar();
    return 0;
}

so that i could see the output.

Right-click on Project -> Properties -> debugging -> Command Arguments.

This was empty in my project and i added the character a to simulate your problem.

Here is the output i am getting:

Right click on the project -> Debug -> Start new Instance -> would you like to build it -> yes

Output:

Command-line argument count: 2
Arguments:
  argv[0]   <my macines path>\helpingStack1.exe
  argv[1]   a

Please check this again. I hope this helps.

1) I am suspecting that your binaries are not up to date when you run this script so please do a clean build and verify that you are indeed running the same exe as the one you are building. Please check the configuration - Debug/Release.

2) go to the folder where you have created the project and righclick on the project folder, and change property -> ensure read only is not checked in the check box.

Upvotes: 1

Related Questions