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

Function and instruction breakpoint log message

未关闭
  • 哪里不对？
#569 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
json
领域
api

调研方向

该 issue 指出了 FunctionBreakpoint 和 InstructionBreakpoint 的 schema 定义；在协议 schema 中找到这些定义，并比较它们现有的 breakpoint 属性。将提议的 logMessage 字段添加到两者中，然后验证两个 schema 是否以一致的方式公开该字段。

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

描述

There is not really any reason for them to not support logMessage field. This was raised in #114, but that post includes different issues as well.

"FunctionBreakpoint": {
	"type": "object",
	"description": "Properties of a breakpoint passed to the `setFunctionBreakpoints` request.",
	"properties": {
		"name": {
			"type": "string",
			"description": "The name of the function."
		},
		"condition": {
			"type": "string",
			"description": "An expression for conditional breakpoints.\nIt is only honored by a debug adapter if the corresponding capability `supportsConditionalBreakpoints` is true."
		},
		"hitCondition": {
			"type": "string",
			"description": "An expression that controls how many hits of the breakpoint are ignored.\nThe debug adapter is expected to interpret the expression as needed.\nThe attribute is only honored by a debug adapter if the corresponding capability `supportsHitConditionalBreakpoints` is true."
		},
+		"logMessage": {
+			"type": "string",
+			"description": "If this attribute exists and is non-empty, the debug adapter must not 'break' (stop)\nbut log the message instead. Expressions within `{}` are interpolated.\nThe attribute is only honored by a debug adapter if the corresponding capability `supportsLogPoints` is true.\nIf either `hitCondition` or `condition` is specified, then the message should only be logged if those conditions are met."
+		}
	},
	"required": [ "name" ]
},

"InstructionBreakpoint": {
	"type": "object",
	"description": "Properties of a breakpoint passed to the `setInstructionBreakpoints` request",
	"properties": {
		"instructionReference": {
			"type": "string",
			"description": "The instruction reference of the breakpoint.\nThis should be a memory or instruction pointer reference from an `EvaluateResponse`, `Variable`, `StackFrame`, `GotoTarget`, or `Breakpoint`."
		},
		"offset": {
			"type": "integer",
			"description": "The offset from the instruction reference in bytes.\nThis can be negative."
		},
		"condition": {
			"type": "string",
			"description": "An expression for conditional breakpoints.\nIt is only honored by a debug adapter if the corresponding capability `supportsConditionalBreakpoints` is true."
		},
		"hitCondition": {
			"type": "string",
			"description": "An expression that controls how many hits of the breakpoint are ignored.\nThe debug adapter is expected to interpret the expression as needed.\nThe attribute is only honored by a debug adapter if the corresponding capability `supportsHitConditionalBreakpoints` is true."
		},
+		"logMessage": {
+			"type": "string",
+			"description": "If this attribute exists and is non-empty, the debug adapter must not 'break' (stop)\nbut log the message instead. Expressions within `{}` are interpolated.\nThe attribute is only honored by a debug adapter if the corresponding capability `supportsLogPoints` is true.\nIf either `hitCondition` or `condition` is specified, then the message should only be logged if those conditions are met."
+		},
		"mode": {
			"type": "string",
			"description": "The mode of this breakpoint. If defined, this must be one of the `breakpointModes` the debug adapter advertised in its `Capabilities`."
		}
	},
	"required": [ "instructionReference" ]
},
主要语言
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

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

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