From d94a40931e7d36ac4dd120b57de638ff24091b89 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Rydg=C3=A5rd?= Date: Wed, 19 Aug 2026 00:49:03 +0200 Subject: [PATCH] Log the debugger port at NOTICE, remove fprintf logging of the port --- Core/WebServer.cpp | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/Core/WebServer.cpp b/Core/WebServer.cpp index d293f2c7dc..e2b99c5f35 100644 --- a/Core/WebServer.cpp +++ b/Core/WebServer.cpp @@ -819,18 +819,11 @@ static void WebServerThread() { RegisterServer(http->Port()); double lastRegister = time_now_d(); - INFO_LOG(Log::HTTP, "Entering web server loop. Listening on port %d", g_Config.iRemoteISOPort); + // NOTICE rather than INFO on purpose: with --debugger=0 the port is picked for us, and this + // line is the only way a client can find out which one it got. + NOTICE_LOG(Log::HTTP, "Entering web server loop. Listening on port %d", g_Config.iRemoteISOPort); if (serverFlags & WebServerFlags::DEBUGGER) { - // And say it once more straight to stderr, outside the log system entirely. A tool that - // launches us (Tools/wsdbg --launch) has to learn the port from our output before it can - // connect to anything, so that one line must not be losable to a log level, a disabled - // channel, or a build that never installs a log output at all. -#if !defined(__LIBRETRO__) - fprintf(stderr, "Debugger listening on port %d\n", g_Config.iRemoteISOPort); - fflush(stderr); -#endif - g_OSD.Show(OSDType::MESSAGE_SUCCESS, "Debugger web server running on port " + std::to_string(g_Config.iRemoteISOPort), 5.0f, "debugger"); g_OSD.SetClickCallback("debugger", []() { OpenWebDebugger();