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

Where are PDB files for public builds? #16452

New Issue
Closed
opened 2026-01-31 05:12:39 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 05:12:39 +00:00
Owner
Copy Link

Originally created by @dmchurch on GitHub (Jan 19, 2022).

Originally assigned to: @DHowett on GitHub.

I've been experiencing occasional hangs in the latest WT (1.11.3471.0 from the Store, on Windows 10.0.22000). I started to debug one myself, partly to help out and partly because it would have been nice to get those six or seven terminal sessions back, but I ran into an issue when VS2022 couldn't find the PDB files for the WT modules. I can see a number of issues here relating to how the PDBs are produced, but I couldn't find anywhere that said where to actually find them. Help? If they aren't getting added to the Microsoft public symbol servers, can someone add something to the docs or the wiki here on where they can be found? Thanks!

Originally created by @dmchurch on GitHub (Jan 19, 2022). Originally assigned to: @DHowett on GitHub. I've been experiencing occasional hangs in the latest WT (1.11.3471.0 from the Store, on Windows 10.0.22000). I started to debug one myself, partly to help out and partly because it would have been nice to get those six or seven terminal sessions back, but I ran into an issue when VS2022 couldn't find the PDB files for the WT modules. I can see a number of issues here relating to how the PDBs are produced, but I couldn't find anywhere that said where to actually find them. Help? If they aren't getting added to the Microsoft public symbol servers, can someone add something to the docs or the wiki here on where they _can_ be found? Thanks!
claunia commented 2026-01-31 05:12:40 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Jan 20, 2022):

@dmchurch the easiest way to get the PDBs is to build WT locally.

@elsaco commented on GitHub (Jan 20, 2022): @dmchurch the easiest way to get the PDBs is to build WT locally.
claunia commented 2026-01-31 05:12:40 +00:00
Author
Owner
Copy Link

@dmchurch commented on GitHub (Jan 20, 2022):

@elsaco Wait, does that work? Can the PDBs from a local build be used to debug the official binaries? I was under the impression you need PDBs created during the build that made your executable.

@dmchurch commented on GitHub (Jan 20, 2022): @elsaco Wait, does that work? Can the PDBs from a local build be used to debug the official binaries? I was under the impression you need PDBs created during the build that made your executable.
claunia commented 2026-01-31 05:12:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 20, 2022):

I know that @DHowett knows the answer to this, I just can't find it by searching the repo for whatever reason ¯\_(ツ)_/¯

@zadjii-msft commented on GitHub (Jan 20, 2022): I know that @DHowett knows the answer to this, I just can't find it by searching the repo for whatever reason ¯\\\_(ツ)_/¯
claunia commented 2026-01-31 05:12:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 24, 2022):

#2857 and #3138 implies we link them somehow... Maybe only WinDBG can figure out where the symbols are...

@zadjii-msft commented on GitHub (Jan 24, 2022): #2857 and #3138 implies we link them somehow... Maybe only WinDBG can figure out where the symbols are...
claunia commented 2026-01-31 05:12:41 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 1, 2022):

This one is on me -- we should certainly be publishing symbols publicly to let folks diagnose in the wild. Thanks for bringing it up :)

@DHowett commented on GitHub (Feb 1, 2022): This one is on me -- we should certainly be publishing symbols publicly to let folks diagnose in the wild. Thanks for bringing it up :)
claunia commented 2026-01-31 05:12:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 4, 2022):

Didn't we do this in https://github.com/microsoft/terminal/pull/11852? Not sure where those go though...

@zadjii-msft commented on GitHub (Feb 4, 2022): Didn't we do this in https://github.com/microsoft/terminal/pull/11852? Not sure where those go though...
claunia commented 2026-01-31 05:12:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 4, 2022):

Nah, that was something slightly different. I've engaged the folks who own the public symbol server and gotten clearance to push there! Today or Monday, I'll upload some historical symbols and make sure the build does so on its own in the future.

@DHowett commented on GitHub (Feb 4, 2022): Nah, that was something slightly different. I've engaged the folks who own the public symbol server and gotten clearance to push there! Today or Monday, I'll upload some historical symbols and make sure the build does so on its own in the future.
claunia commented 2026-01-31 05:12:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 8, 2022):

Got a PR out to make sure we publish these :)

@DHowett commented on GitHub (Feb 8, 2022): Got a PR out to make sure we publish these :)
claunia commented 2026-01-31 05:12:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 11, 2022):

:tada:This issue was addressed in #12441, which has now been successfully released as Windows Terminal v1.12.10393.0.🎉

Handy links:

@ghost commented on GitHub (Feb 11, 2022): :tada:This issue was addressed in #12441, which has now been successfully released as `Windows Terminal v1.12.10393.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.12.10393.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 05:12:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 11, 2022):

:tada:This issue was addressed in #12441, which has now been successfully released as Windows Terminal Preview v1.13.10395.0.🎉

Handy links:

@ghost commented on GitHub (Feb 11, 2022): :tada:This issue was addressed in #12441, which has now been successfully released as `Windows Terminal Preview v1.13.10395.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.13.10395.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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 Issue-Docs Issue-Question Needs-Tag-Fix Priority-3 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#16452
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?