Windows应用中如何同时显示窗口与CMD并查看OutputDebugString输出？

Got it, let's tackle this problem step by step. You want your Windows GUI app to display both its main window and a console window to view debugging messages (either redirected from OutputDebugString or directly printed), and fix the issue where the console closes immediately when launching from command line. Here are two solid approaches:

Approach 1: Switch to Console Subsystem (with WinMain Entry) #

This method modifies your project's linker settings to natively create both a console and your GUI window.

1. Update Linker Subsystem

   • In Visual Studio, right-click your project → Properties → Linker → System → Subsystem.
   • Select Console (/SUBSYSTEM:CONSOLE) instead of Windows (/SUBSYSTEM:WINDOWS).

2. Set Custom Entry Point

   • Since your app uses WinMain (not main) as the entry point, go to Linker → Advanced → Entry Point.
   • Enter WinMainCRTStartup (this tells the linker to use the WinMain-based startup code even for the console subsystem).

3. Redirect OutputDebugString to Console
   OutputDebugString sends messages to a debugger (like Visual Studio's Output window) by default, not the console. To see those messages in the console, wrap the function with a macro that also prints to stdout:

   #include <stdio.h>
   #include <windows.h>
   
   #define DBG_LOG(fmt, ...) \
       do { \
           char buffer[1024]; \
           sprintf_s(buffer, sizeof(buffer), fmt, __VA_ARGS__); \
           OutputDebugStringA(buffer); \
           printf("%s\n", buffer); \
       } while(0)
   
   // Use it like this in your code:
   DBG_LOG("Window initialized with handle: %p", hwnd);
   

Now when you run the app, both the console and your GUI window will appear. The console will stay open until your app exits, whether you launch it from Visual Studio or the command line.

Approach 2: Dynamically Allocate a Console (Keep Windows Subsystem) #

If you want to keep the Windows subsystem (no linker setting changes), you can create a console window at runtime. This is perfect if you only want the console to appear in debug builds.

Add this code at the start of your WinMain function:

#include <windows.h>
#include <stdio.h>

int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nShowCmd)
{
    // Create a console window
    if (!AllocConsole()) {
        MessageBoxA(NULL, "Failed to allocate console", "Error", MB_ICONERROR);
    }

    // Redirect stdout/stderr to the console so printf works
    FILE* consoleOut;
    freopen_s(&consoleOut, "CONOUT$", "w", stdout);
    freopen_s(&consoleOut, "CONOUT$", "w", stderr);

    // Use the same DBG_LOG macro from Approach 1 to send messages to both debugger and console
    DBG_LOG("Console allocated successfully");

    // Your existing window creation and message loop code goes here...
    // Example window setup:
    WNDCLASSEXA wc = {0};
    wc.cbSize        = sizeof(WNDCLASSEXA);
    wc.lpfnWndProc   = DefWindowProcA;
    wc.hInstance     = hInstance;
    wc.lpszClassName = "MyAppWindowClass";
    RegisterClassExA(&wc);

    HWND hwnd = CreateWindowExA(
        0, "MyAppWindowClass", "My GUI App", WS_OVERLAPPEDWINDOW,
        CW_USEDEFAULT, CW_USEDEFAULT, 640, 480,
        NULL, NULL, hInstance, NULL
    );
    ShowWindow(hwnd, nShowCmd);

    // Message loop
    MSG msg;
    while (GetMessage(&msg, NULL, 0, 0)) {
        TranslateMessage(&msg);
        DispatchMessage(&msg);
    }

    // Clean up the console when the app exits
    FreeConsole();
    return (int)msg.wParam;
}

Key Notes: #

• When using Approach 2, launching from the command line won't close the console immediately because the console is now part of your app's process.
• If you just want to view OutputDebugString messages without redirecting to console, you can use tools like DebugView to capture all debug messages system-wide, but the above methods let you see them directly in a console alongside your GUI.

内容的提问来源于stack exchange，提问作者user11157650