Add debuginfod launch option documentation for C/C++ debugging#9819
Add debuginfod launch option documentation for C/C++ debugging#9819WardenGnaw wants to merge 2 commits into
Conversation
|
At what point do the docs update compared to when the fix gets shipped to insiders or release? We're not sure when our next insiders release will be because we're still working on fixes. Although if you really want, theoretically we could cherry-pick your fix to get it into releases sooner. |
|
@WardenGnaw Let me know when this can be merged and published. |
@ntrogh That's what I'm unclear about -- when do doc updates normally get released? When available in the latest pre-release or release? I think we may not release our next pre-release till the week of June 1. |
@sean-mcmanus By default, docs reflect stable releases, unless prefaced otherwise. |
Ah, okay. We don't yet have an ETA on when our 1.33.x stable will get released since it has major changes that are potentially destabilizing. I'll let you know when we release that. |
WardenGnaw
force-pushed
the
dev/waan/updateCppDebuginfod
branch
from
f6035f9 to
311c19e
Compare
Document the new `debuginfod` configuration option in launch.json that controls GDB's debuginfod behavior. This option was added to MIEngine to prevent GDB hangs when debuginfod servers are unreachable
The debuginfod.enabled property defaults to false, not true, matching the cpptools extension source. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
WardenGnaw
force-pushed
the
dev/waan/updateCppDebuginfod
branch
from
311c19e to
2f0d6e6
Compare
|
Updating docs since we are making the default value of enabled false. |
5 participants
Document the new
debuginfodconfiguration option in launch.json that controls GDB's debuginfod behavior. This option was added to MIEngine to prevent GDB hangs when debuginfod servers are unreachable