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

Bug Report : ls (gnuwin32) command cause terminal to shutdown away in CMD window #2536

New Issue
Closed
opened 2026-01-30 22:57:39 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 22:57:39 +00:00
Owner
Copy Link

Originally created by @f-quintero on GitHub (Jul 3, 2019).

Originally assigned to: @carlos-zamora on GitHub.

Environment

Windows 10 pro
Lenovo T470
GnuWin32 installed
CMD Windows
Windows terminal version: 0.2.1715.0

C:\Users\fabian.quintero>where ls C:\gnuwin32\bin\ls.exe
C:\Users\fabian.quintero>ls --version
ls (GNU coreutils) 5.3.0
Escrito por Richard Stallman y David MacKenzie.

Copyright (C) 2005 Free Software Foundation, Inc.
Esto es software libre; vea el código fuente para las condiciones de copia.
No hay NINGUNA garantía; ni siquiera de COMERCIABILIDAD o IDONEIDAD PARA UN
FIN DETERMINADO.

C:\gnuwin32\bin is in the PATH environment variable

Steps to reproduce

  1. Start Windows terminal (preview)
    this start on powershell window
  2. Start CMD window
  3. Close the first powershell window
  4. start a new powershell window
  5. close the new powershell window
  6. on the unique Windows (CMD) run the ls -l commnad
    result: Windows Terminal crash

show the debug option. Start debug. This do nos show source. Detailed exption info is;
Excepción no controlada en 0x0000000000000074 en WindowsTerminal.exe: 0xC0000005: Infracción de acceso al ejecutar la ubicación 0x0000000000000074.

ls -l Works fine in others sequence

Expected behavior

A normal end of the ls -l command.

Actual behavior

Described above.

Originally created by @f-quintero on GitHub (Jul 3, 2019). Originally assigned to: @carlos-zamora on GitHub. <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Windows 10 pro Lenovo T470 GnuWin32 installed CMD Windows Windows terminal version: 0.2.1715.0 C:\Users\fabian.quintero>where ls C:\gnuwin32\bin\ls.exe C:\Users\fabian.quintero>ls --version ls (GNU coreutils) 5.3.0 Escrito por Richard Stallman y David MacKenzie. Copyright (C) 2005 Free Software Foundation, Inc. Esto es software libre; vea el código fuente para las condiciones de copia. No hay NINGUNA garantía; ni siquiera de COMERCIABILIDAD o IDONEIDAD PARA UN FIN DETERMINADO. C:\gnuwin32\bin is in the PATH environment variable # Steps to reproduce 1) Start Windows terminal (preview) this start on powershell window 2) Start CMD window 3) Close the first powershell window 4) start a new powershell window 5) close the new powershell window 6) on the unique Windows (CMD) run the ls -l commnad result: Windows Terminal crash show the debug option. Start debug. This do nos show source. Detailed exption info is; Excepción no controlada en 0x0000000000000074 en WindowsTerminal.exe: 0xC0000005: Infracción de acceso al ejecutar la ubicación 0x0000000000000074. ls -l Works fine in others sequence # Expected behavior A normal end of the ls -l command. # Actual behavior <!-- What's actually happening? --> Described above.
claunia added the Needs-TriageNeeds-AttentionResolution-Duplicate labels 2026-01-30 22:57:39 +00:00
claunia commented 2026-01-30 22:57:40 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 3, 2019):

Does it happen if you just open and close powershell tabs without running "ls"?

@DHowett-MSFT commented on GitHub (Jul 3, 2019): Does it happen if you just open and close powershell tabs without running "ls"?
claunia commented 2026-01-30 22:57:41 +00:00
Author
Owner
Copy Link

@f-quintero commented on GitHub (Jul 3, 2019):

Hi,

yes, if i run commands in each windows, then when finally i run the LS on the CMD windows this works fine.

De: Dustin L. Howett (MSFT) notifications@github.com
Enviado: miércoles, 3 de julio de 2019 1:57 p. m.
Para: microsoft/terminal
Cc: f-quintero; Author
Asunto: Re: [microsoft/terminal] Bug Report : ls (gnuwin32) command cause terminal to shutdown away in CMD window (#1806)

Does it happen if you just open and close powershell tabs without running "ls"?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/terminal/issues/1806?email_source=notifications&email_token=AMQRRTM36EZ25CSDQWUMA6DP5TZDPA5CNFSM4H5ISB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFMJ6Q#issuecomment-508216570, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMQRRTNUL7NTVBHZTSNZZBLP5TZDPANCNFSM4H5ISB3A.

@f-quintero commented on GitHub (Jul 3, 2019): Hi, yes, if i run commands in each windows, then when finally i run the LS on the CMD windows this works fine. ________________________________ De: Dustin L. Howett (MSFT) <notifications@github.com> Enviado: miércoles, 3 de julio de 2019 1:57 p. m. Para: microsoft/terminal Cc: f-quintero; Author Asunto: Re: [microsoft/terminal] Bug Report : ls (gnuwin32) command cause terminal to shutdown away in CMD window (#1806) Does it happen if you just open and close powershell tabs without running "ls"? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://github.com/microsoft/terminal/issues/1806?email_source=notifications&email_token=AMQRRTM36EZ25CSDQWUMA6DP5TZDPA5CNFSM4H5ISB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFMJ6Q#issuecomment-508216570>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMQRRTNUL7NTVBHZTSNZZBLP5TZDPANCNFSM4H5ISB3A>.
claunia commented 2026-01-30 22:57:41 +00:00
Author
Owner
Copy Link

@JL2210 commented on GitHub (Jul 3, 2019):

GnuWin32 is ancient and hasn't been updated in a long time.

@JL2210 commented on GitHub (Jul 3, 2019): GnuWin32 is ancient and hasn't been updated in a long time.
claunia commented 2026-01-30 22:57:41 +00:00
Author
Owner
Copy Link

@f-quintero commented on GitHub (Jul 3, 2019):

Yes it is, i hope final version of Windows Terminal will handle this kind of software in a elegant way, like cmd.exe.

De: James Larrowe notifications@github.com
Enviado: miércoles, 3 de julio de 2019 2:55 p. m.
Para: microsoft/terminal
Cc: f-quintero; Author
Asunto: Re: [microsoft/terminal] Bug Report : ls (gnuwin32) command cause terminal to shutdown away in CMD window (#1806)

GnuWin32 is ancient and hasn't been updated in a long time.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/terminal/issues/1806?email_source=notifications&email_token=AMQRRTNWJLDK3OULI7KUP3TP5T74HA5CNFSM4H5ISB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFQOUI#issuecomment-508233553, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMQRRTNYWSTJMCFCYXV52WLP5T74HANCNFSM4H5ISB3A.

@f-quintero commented on GitHub (Jul 3, 2019): Yes it is, i hope final version of Windows Terminal will handle this kind of software in a elegant way, like cmd.exe. ________________________________ De: James Larrowe <notifications@github.com> Enviado: miércoles, 3 de julio de 2019 2:55 p. m. Para: microsoft/terminal Cc: f-quintero; Author Asunto: Re: [microsoft/terminal] Bug Report : ls (gnuwin32) command cause terminal to shutdown away in CMD window (#1806) GnuWin32 is ancient and hasn't been updated in a long time. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://github.com/microsoft/terminal/issues/1806?email_source=notifications&email_token=AMQRRTNWJLDK3OULI7KUP3TP5T74HA5CNFSM4H5ISB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFQOUI#issuecomment-508233553>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMQRRTNYWSTJMCFCYXV52WLP5T74HANCNFSM4H5ISB3A>.
claunia commented 2026-01-30 22:57:42 +00:00
Author
Owner
Copy Link

@f-quintero commented on GitHub (Jul 6, 2019):

Hi,

I get the same result on another computer, with the same software versions. This is a consistent problem.

Enviado desde Correohttps://go.microsoft.com/fwlink/?LinkId=550986 para Windows 10

De: James Larrowe notifications@github.com
Enviado: Wednesday, July 3, 2019 2:55:47 PM
Para: microsoft/terminal
Cc: f-quintero; Author
Asunto: Re: [microsoft/terminal] Bug Report : ls (gnuwin32) command cause terminal to shutdown away in CMD window (#1806)

GnuWin32 is ancient and hasn't been updated in a long time.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/terminal/issues/1806?email_source=notifications&email_token=AMQRRTNWJLDK3OULI7KUP3TP5T74HA5CNFSM4H5ISB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFQOUI#issuecomment-508233553, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMQRRTNYWSTJMCFCYXV52WLP5T74HANCNFSM4H5ISB3A.

@f-quintero commented on GitHub (Jul 6, 2019): Hi, I get the same result on another computer, with the same software versions. This is a consistent problem. Enviado desde Correo<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows 10 ________________________________ De: James Larrowe <notifications@github.com> Enviado: Wednesday, July 3, 2019 2:55:47 PM Para: microsoft/terminal Cc: f-quintero; Author Asunto: Re: [microsoft/terminal] Bug Report : ls (gnuwin32) command cause terminal to shutdown away in CMD window (#1806) GnuWin32 is ancient and hasn't been updated in a long time. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://github.com/microsoft/terminal/issues/1806?email_source=notifications&email_token=AMQRRTNWJLDK3OULI7KUP3TP5T74HA5CNFSM4H5ISB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFQOUI#issuecomment-508233553>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMQRRTNYWSTJMCFCYXV52WLP5T74HANCNFSM4H5ISB3A>.
claunia commented 2026-01-30 22:57:42 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 12, 2019):

Hola @f-quintero. Queremos saber si el problema esta relacionado con gnuwin32 o con PowerShell. Sabemos que hay un bug que puede aparecer cuando uno cierra PowerShell (hay un crash ☹️ ). Si no abres/cierras ningún tab con PowerShell, y solamente usas CMD en Windows Terminal, este crash ocurre?

Podrias reproducir este crash en el master branch, para ver si puedes agarrar un call stack con mas información?

@carlos-zamora commented on GitHub (Jul 12, 2019): Hola @f-quintero. Queremos saber si el problema esta relacionado con gnuwin32 o con PowerShell. Sabemos que hay un bug que puede aparecer cuando uno cierra PowerShell (hay un crash ☹️ ). Si no abres/cierras ningún tab con PowerShell, y solamente usas CMD en Windows Terminal, este crash ocurre? Podrias reproducir este crash en el _master_ branch, para ver si puedes agarrar un call stack con mas información?
claunia commented 2026-01-30 22:57:42 +00:00
Author
Owner
Copy Link

@f-quintero commented on GitHub (Jul 12, 2019):

Hola Carlos, buenos días.

Powershell siempre se abre, así que la prueba solo la puedo hacer con al menos un powershell.

Prueba 1: Powershell abierto (el que abre por default) y ventana CMD.
Paso 1: inicio Terminal Window
Paso 2: inicio CMD window
Paso 3: ejecuto ls -l

Resultado: No ocurre el crash.

Prueba 2: Cierro el primer powershell el que abre por default.
Paso 1: Inicio Terminal Window
Paso 2: inicio CMD window
Paso 3: cierro el powershell por defecto.
Paso 4: Ejecuto ls -l

Resultado: No ocurre el crash.

Prueba 3: Usar el master branch .... No se como hacerlo.
Tengo instalado VS 2017 Community
De donde descargo el master branch?
Que otro requisito debo obtener?

Saludos,

De: Carlos Zamora notifications@github.com
Enviado: jueves, 11 de julio de 2019 9:56 p. m.
Para: microsoft/terminal
Cc: f-quintero; Mention
Asunto: Re: [microsoft/terminal] Bug Report : ls (gnuwin32) command cause terminal to shutdown away in CMD window (#1806)

Hola @f-quinterohttps://github.com/f-quintero. Queremos saber si el problema esta relacionado con gnuwin32 o con PowerShell. Sabemos que hay un bug que puede aparecer cuando uno cierra PowerShell (hay un crash :( ). Si no abres/cierras ningún tab con PowerShell, y solamente usas CMD en Windows Terminal, este crash ocurre?

Podrias reproducir este crash en el master branch, para ver si puedes agarrar un call stack con mas información?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/terminal/issues/1806?email_source=notifications&email_token=AMQRRTNAU67H55K4T4V7ZO3P67XGBA5CNFSM4H5ISB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZYQ2QQ#issuecomment-510725442, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMQRRTL6OTDUA3KVIZL4QKLP67XGBANCNFSM4H5ISB3A.

@f-quintero commented on GitHub (Jul 12, 2019): Hola Carlos, buenos días. Powershell siempre se abre, así que la prueba solo la puedo hacer con al menos un powershell. Prueba 1: Powershell abierto (el que abre por default) y ventana CMD. Paso 1: inicio Terminal Window Paso 2: inicio CMD window Paso 3: ejecuto ls -l Resultado: No ocurre el crash. Prueba 2: Cierro el primer powershell el que abre por default. Paso 1: Inicio Terminal Window Paso 2: inicio CMD window Paso 3: cierro el powershell por defecto. Paso 4: Ejecuto ls -l Resultado: No ocurre el crash. Prueba 3: Usar el master branch .... No se como hacerlo. Tengo instalado VS 2017 Community De donde descargo el master branch? Que otro requisito debo obtener? Saludos, ________________________________ De: Carlos Zamora <notifications@github.com> Enviado: jueves, 11 de julio de 2019 9:56 p. m. Para: microsoft/terminal Cc: f-quintero; Mention Asunto: Re: [microsoft/terminal] Bug Report : ls (gnuwin32) command cause terminal to shutdown away in CMD window (#1806) Hola @f-quintero<https://github.com/f-quintero>. Queremos saber si el problema esta relacionado con gnuwin32 o con PowerShell. Sabemos que hay un bug que puede aparecer cuando uno cierra PowerShell (hay un crash :( ). Si no abres/cierras ningún tab con PowerShell, y solamente usas CMD en Windows Terminal, este crash ocurre? Podrias reproducir este crash en el master branch, para ver si puedes agarrar un call stack con mas información? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://github.com/microsoft/terminal/issues/1806?email_source=notifications&email_token=AMQRRTNAU67H55K4T4V7ZO3P67XGBA5CNFSM4H5ISB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZYQ2QQ#issuecomment-510725442>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMQRRTL6OTDUA3KVIZL4QKLP67XGBANCNFSM4H5ISB3A>.
claunia commented 2026-01-30 22:57:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 2, 2019):

I'm almost certain this is a dupe of #1445 that's occurring with powershell instead of Ubuntu/WSL. We've seen a bunch of reports of that in various different versions.

If that's not the issue, we can re-open and try and investigate more.

@zadjii-msft commented on GitHub (Aug 2, 2019): I'm almost certain this is a dupe of #1445 that's occurring with powershell instead of Ubuntu/WSL. We've seen a bunch of reports of that in various different versions. If that's _not_ the issue, we can re-open and try and investigate more.
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 Needs-Attention Needs-Triage Resolution-Duplicate
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#2536
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?