Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Allow enumeration of variables without fetching values

未关闭
#564 2 条评论 4 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
c, cpp
领域
devtools

调研方向

从现有的 variables requests 和提议的 VariablesArguments 属性开始,然后检查 Scope 在协议中的表示方式。该 issue 没有指定文件或测试;完成这项工作需要就一个无需获取变量值即可枚举变量的 API 达成一致,并决定是否应在变量视图中隐藏较大的 Scope。

由索引模型根据 Issue 内容生成。

描述

info-needed under-discussion

We are currently investigating features for a debugger for embedded applications that would significantly benefit from mechanisms to enumerate global variables and file static variables of a C/C++ program. Maybe also functions in future.

A lot of what we'd need is already available with variables requests. But I can't find a way to explicitly configure to skip fetching the variable value. This would be important for our embedded use case. We often see applications with lots of global variables. But more importantly, even a moderate number of global variables can mean many target accesses which can be expensive and impact performance if you are using a JTAG debugger.

Would a new VariablesArguments property to skip reading values make sense? Or an entirely new API function for symbol/variable enumeration without fetching values?

Also, thinking about the huge number of global variables that can be returned, it could make sense to put them into a Scope that has a flag marking it as "do-not-show" in a variables window/GUI. Navigating the huge number of variables may not be practical. But you may still want to list them and their properties in other views and send them for example to a Watch window.

I was briefly thinking into the direction of using a language server for the enumeration. But in our experience, you better rely on the debugger/debug adapter to be the single source of truth of what really exists in the debug information/symbol tables of the debugged application.

主要语言
HTML
星标
1.8k
派生
173
平均合并
7 天 7 小时
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/debug-adapter-protocol 的其他 Issue

查看 microsoft/debug-adapter-protocol 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。