mirrors/bun.sh
1
0
Fork 0
mirror of https://github.com/oven-sh/bun synced 2026-02-02 15:08:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update debugger things (#8180)

Browse Source 
* T

* Update Debug Adapter Protocol

* Update JSC and V8 debugger protocols

* Update inspector-frontend

* Fix empty keys not being printed in `console.log`

* Add `bun --inspect` tests and fix edge cases

* bun install --exact
This commit is contained in:
Ashcon Partovi
2024-01-15 17:00:29 -08:00
committed by GitHub
parent 611b296a6a
commit 2d21567271
20 changed files with 1234 additions and 104 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
packages/bun-debug-adapter-protocol/bun.lockb
View File

Binary file not shown.

15
packages/bun-debug-adapter-protocol/src/protocol/index.d.ts vendored
View File

@@ -2215,7 +2215,7 @@ export namespace DAP {
*/
instructionReference: string;
/**
* The offset from the instruction reference.
* The offset from the instruction reference in bytes.
* This can be negative.
*/
offset?: number;
@@ -2278,6 +2278,13 @@ export namespace DAP {
* This can be negative.
*/
offset?: number;
/**
* A machine-readable explanation of why a breakpoint may not be verified. If a breakpoint is verified or a specific reason is not known, the adapter should omit this property. Possible values include:
*
* - `pending`: Indicates a breakpoint might be verified in the future, but the adapter cannot verify it in the current state.
* - `failed`: Indicates a breakpoint was not able to be verified, and the adapter does not believe it can be verified without intervention.
*/
reason?: "pending" | "failed";
};
/**
* The granularity of one 'step' in the stepping requests `next`, `stepIn`, `stepOut`, and `stepBack`.
@@ -2587,6 +2594,12 @@ export namespace DAP {
* The end column of the range that corresponds to this instruction, if any.
*/
endColumn?: number;
/**
* A hint for how to present the instruction in the UI.
*
* A value of `invalid` may be used to indicate this instruction is 'filler' and cannot be reached by the program. For example, unreadable memory addresses may be presented is 'invalid.'
*/
presentationHint?: "normal" | "invalid";
};
/**
* Logical areas that can be invalidated by the `invalidated` event.

12
packages/bun-debug-adapter-protocol/src/protocol/protocol.json
View File

@@ -3420,7 +3420,7 @@
},
"offset": {
"type": "integer",
"description": "The offset from the instruction reference.\nThis can be negative."
"description": "The offset from the instruction reference in bytes.\nThis can be negative."
},
"condition": {
"type": "string",
@@ -3467,6 +3467,11 @@
"offset": {
"type": "integer",
"description": "The offset from the instruction reference.\nThis can be negative."
},
"reason": {
"type": "string",
"description": "A machine-readable explanation of why a breakpoint may not be verified. If a breakpoint is verified or a specific reason is not known, the adapter should omit this property. Possible values include:\n\n- `pending`: Indicates a breakpoint might be verified in the future, but the adapter cannot verify it in the current state.\n - `failed`: Indicates a breakpoint was not able to be verified, and the adapter does not believe it can be verified without intervention.",
"enum": ["pending", "failed"]
}
},
"required": ["verified"]
@@ -3750,6 +3755,11 @@
"endColumn": {
"type": "integer",
"description": "The end column of the range that corresponds to this instruction, if any."
},
"presentationHint": {
"type": "string",
"description": "A hint for how to present the instruction in the UI.\n\nA value of `invalid` may be used to indicate this instruction is 'filler' and cannot be reached by the program. For example, unreadable memory addresses may be presented is 'invalid.'",
"enum": ["normal", "invalid"]
}
},
"required": ["address", "instruction"]