starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Unexpected debug logs when typing in a conhost WSL shell #2906

New Issue
Closed
opened 2026-01-30 23:08:30 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 23:08:30 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Jul 24, 2019).

Environment

Windows build number: Version 10.0.18362.175
Windows Terminal version (if applicable): Built locally from commit dca0ffe6dd

Steps to reproduce

  1. Start conhost (Host.exe) from within the Visual Studio debugger.
  2. From the cmd prompt, open a WSL bash shell.
  3. Begin typing something on the command line.
  4. Watch the Output/Debug window in Visual Studio.
  5. Note the constant stream of debug messages being generated as you type.

Expected behavior

I wouldn't expect to see much of anything in the debug output unless there was a genuine error condition.

Actual behavior

It seems that for every key press I get a pair of debug messages similar to this:

...\terminal\src\host\directio.cpp(317)\OpenConsole.exe!00007FF764908C40: (caller: 00007FF76494E601) ReturnHr(19) tid(2c6c) D0030001
...\terminal\src\host\directio.cpp(387)\OpenConsole.exe!00007FF764908D00: (caller: 00007FF76494E606) ReturnHr(20) tid(2c6c) D0030001

As far as I can make out, the issue is that _DoGetConsoleInput method can successfully return either a STATUS_SUCCESS or a CONSOLE_STATUS_WAIT, but the latter is considered an error by the RETURN_NTSTATUS macro, so it's logged in the debug output.

I guess it's possible that's intentional, but I suspect it's more likely an oversight. If it's an expected outcome, I wouldn't think you'd want to keep flooding the logs with those messages. It makes it difficult to spot any real errors, and it's probably not helping performance.

Originally created by @j4james on GitHub (Jul 24, 2019). # Environment Windows build number: Version 10.0.18362.175 Windows Terminal version (if applicable): Built locally from commit dca0ffe6dd0f76ca7997807424a2c08684e07751 # Steps to reproduce 1. Start conhost (Host.exe) from within the Visual Studio debugger. 2. From the cmd prompt, open a WSL bash shell. 3. Begin typing something on the command line. 4. Watch the Output/Debug window in Visual Studio. 5. Note the constant stream of debug messages being generated as you type. # Expected behavior I wouldn't expect to see much of anything in the debug output unless there was a genuine error condition. # Actual behavior It seems that for every key press I get a pair of debug messages similar to this: ...\terminal\src\host\directio.cpp(317)\OpenConsole.exe!00007FF764908C40: (caller: 00007FF76494E601) ReturnHr(19) tid(2c6c) D0030001 ...\terminal\src\host\directio.cpp(387)\OpenConsole.exe!00007FF764908D00: (caller: 00007FF76494E606) ReturnHr(20) tid(2c6c) D0030001 As far as I can make out, the issue is that `_DoGetConsoleInput` method can successfully return either a `STATUS_SUCCESS` or a `CONSOLE_STATUS_WAIT`, but the latter is considered an error by the `RETURN_NTSTATUS` macro, so it's logged in the debug output. I guess it's possible that's intentional, but I suspect it's more likely an oversight. If it's an expected outcome, I wouldn't think you'd want to keep flooding the logs with those messages. It makes it difficult to spot any real errors, and it's probably not helping performance.
claunia commented 2026-01-30 23:08:31 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Aug 1, 2019):

Yes, that's an oversight. It should be using either the _EXPECTED version of the macros so it doesn't report or somehow skipping the macro for those scenarios as the debug message is not useful.

@miniksa commented on GitHub (Aug 1, 2019): Yes, that's an oversight. It should be using either the _EXPECTED version of the macros so it doesn't report or somehow skipping the macro for those scenarios as the debug message is not useful.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Input Help Wanted Issue-Bug Product-Conhost Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2906
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?