-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Closed
Copy link
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeededVerification succeeded
Milestone
Description
Issue Type: Bug
After installation 1.28.1, updated from version 1.27.2, my debug extension does not show the entire "call stack".
Previous behavior (1.27.2):
The stack was fully displayed:

New behavior (1.28.1):
If the source code is not found in the folder (s) the stack item is not displayed:

My debug extension sends the following json response to the StackTrace request:
{
"seq":19,
"success":true,
"message":null,
"request_seq":9,
"command":"stackTrace",
"body":{
"stackFrames":[
{
"id":1001,
"source":{
"name":"test.tlpp",
"path":"c:\\vscode\\tlpp-unit-test\\test\\test.tlpp",
"sourceReference":0
},
"line":10,
"column":0,
"name":"U_MYFINAL"
},
{
"id":1002,
"source":{
"name":"APLIB190.PRW",
"path":"APLIB190.PRW",
"sourceReference":0
},
"line":164,
"column":0,
"name":"EXECBLOCK"
},
{
"id":1003,
"source":{
"name":"MSFINAL.PRW",
"path":"MSFINAL.PRW",
"sourceReference":0
},
"line":64,
"column":0,
"name":"FINAL"
},
{
"id":1004,
"source":{
"name":"FWAPP.PRW",
"path":"FWAPP.PRW",
"sourceReference":0
},
"line":600,
"column":0,
"name":"{ || PSWWPCOMMIT())}"
},
{
"id":1005,
"source":{
"name":"FWAPP.PRW",
"path":"FWAPP.PRW",
"sourceReference":0
},
"line":714,
"column":0,
"name":"{ || EVAL(BCLOSE)}"
},
{
"id":1006,
"source":{
"name":"FWAPP.PRW",
"path":"FWAPP.PRW",
"sourceReference":0
},
"line":714,
"column":0,
"name":"ACTIVATE"
},
{
"id":1007,
"source":{
"name":"APLIB000.PRW",
"path":"APLIB000.PRW",
"sourceReference":0
},
"line":123,
"column":0,
"name":"SIGAFAT"
}
]
},
"type":"response"
}
Has something changed that I need to implement in my extension?
PSC
I tested the insiders and behavior continues the same as 1.28.1.
VS Code version: Code 1.28.1 (3368db6, 2018-10-11T18:13:53.910Z)
OS version: Windows_NT x64 10.0.15063
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 2904) |
| GPU Status | 2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled |
| Memory (System) | 15.87GB (8.19GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
Extensions (10)
| Extension | Author (truncated) | Version |
|---|---|---|
| numbered-bookmarks | ale | 0.12.0 |
| tslint | eg2 | 1.0.40 |
| advpl-vscode | Kil | 0.10.12 |
| cmake-tools-helper | mad | 0.2.1 |
| Angular-BeastCode | Mik | 6.2.32 |
| cpptools | ms- | 0.19.0 |
| debugger-for-chrome | msj | 4.10.2 |
| vscode-coverage-gutters | rya | 2.2.0 |
| cmake | twx | 0.0.17 |
| cmake-tools | vec | 1.1.2 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeededVerification succeeded