Solved

Killing a console application

Posted on 2004-10-29
1,223 Views
Last Modified: 2013-12-03
I have a console application that closes by capturing CTRL_CLOSE_EVENT message.
If I startup this application manually, and then close the DOS console window via the CLOSE [X] icon, the applications closes successfully.
I can verify that it closes successfully, because I can see the debug log file showing that it captured the CTRL_CLOSE_EVENT message.

Now here is where my problem is at.  I have a test application that is suppose to launch the above console application, and then after peformming the proper test, it suppose to signal to the console application to close.  However, I can't seem to get the console application to close programmatically.
Here's the code that is in the test application:

            STARTUPINFO si;
            PROCESS_INFORMATION pi;
            char TargetExec[] = "..\\debug\\FileBridgeApp.exe";
            
            ZeroMemory( &si, sizeof(si) );
            si.cb = sizeof(si);
            ZeroMemory( &pi, sizeof(pi) );
            if (CreateProcess( NULL,      // No module name (use command line).
                        TargetExec,                  // Command line.
                        NULL,                        // Process handle not inheritable.
                        NULL,                        // Thread handle not inheritable.
                        FALSE,                        // Set handle inheritance to FALSE.
                        0,                              // No creation flags.
                        NULL,                        // Use parent's environment block.
                        NULL,                        // Use parent's starting directory.
                        &si,                        // Pointer to STARTUPINFO structure.
                        &pi )                        // Pointer to PROCESS_INFORMATION structure.
                  )
            {
                  CreateFilesInMonitoringDirectorys(teststructure, QtyTestApp);
                  // Close process and thread handles.
                  CloseHandle( pi.hProcess ); // ******this does not close the application
                  CloseHandle( pi.hThread ); // ******this does not close the application

How can  correctly signal to the application to close.
0
Question by:Axter
    7 Comments
     
    LVL 48

    Expert Comment

    by:Mikal613
    0
     
    LVL 30

    Author Comment

    by:Axter
    That link is about capturing CTRL_CLOSE_EVENT message.

    As I stated in my question, I'm not having a problem with capturing the message.

    My problem is with the test application sending the message.
    0
     
    LVL 86

    Accepted Solution

    by:
    >>CloseHandle( pi.hProcess ); // ******this does not close the application

    Well, it only closes the process handle. See http://support.microsoft.com/kb/q178893/ ("How To Terminate an Application "Cleanly" in Win32").
    0
     
    LVL 30

    Author Comment

    by:Axter
    Thanks jkr.

    I replace CloseHandle lines with the following:
    EnumWindows((WNDENUMPROC)TerminateAppEnum, (LPARAM) pi.dwProcessId) ;

    And copied and pasted the TerminateAppEnum function to my test project, and that seem to have done the trick.
    0
     
    LVL 86

    Expert Comment

    by:jkr
    Um, sorry to be nitpicking, but you still should call 'CloseHandle()' even after terminating the console process. The "costs" in user space (4 bytes for the handle) is not important, but...
    0
     
    LVL 30

    Author Comment

    by:Axter
    >>you still should call 'CloseHandle()'

    What is gain by that?
    When the console application shutsdown, wouldn't it close the process and the threads?
    0
     
    LVL 86

    Expert Comment

    by:jkr
    For the app you're terminating, that's it. But, the calling app is still responsible to free the control structures (IOW: What's 'behind' the handle). It's not that much of memory, but that might add up e.g. in a server app in the long run.
    0

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Suggested Solutions

    This article shows how to make a Windows 7 gadget that accepts files dropped from the Windows Explorer.  It also illustrates how to give your gadget a non-rectangular shape and how to add some nifty visual effects to text displayed in a your gadget.…
    If you have ever found yourself doing a repetitive action with the mouse and keyboard, and if you have even a little programming experience, there is a good chance that you can use a text editor to whip together a sort of macro to automate the proce…
    This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…
    This video discusses moving either the default database or any database to a new volume.

    913 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now