Skip to content

Allow Hierarchical call stack view - #35

Merged
aragners merged 1 commit into
intel:mainfrom
aragners:call-stack-hierarchical
Nov 17, 2026
Merged

aragners merged 1 commit into
intel:mainfrom
aragners:call-stack-hierarchical

Conversation

@aragners

Copy link
Copy Markdown
Contributor

The Call Stack view shows the run control context hierarchy: each context with child contexts, such as a process of the Linux tracker, is a nested session with its threads.

Turn it off with "callStackHierarchy": false.

"callStackCompact": false gives every context a row of its own. Containers with a single thread show the thread in the session above.

@aragners
aragners requested a review from a team as a code owner November 16, 2026 13:32
@clillies
clillies self-requested a review November 16, 2026 16:47
Comment thread README.md Resolved
clillies
clillies previously approved these changes Nov 16, 2026

@clillies clillies left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't know if the README.md can be made easier to read.
I proposed something.
I also wonder if the configuration texts can be made more clear, but we can do that separatly, the existing are quite babbly before as well.
I saw something while debugging, a frame with unknown address, I'll IM about that.

Comment thread package.json Resolved
The Call Stack view shows the run control context hierarchy: each
context with child contexts, such as a process of the Linux tracker, is
a nested session with its threads.

Turn it off with `"callStackHierarchy": false`.

`"callStackCompact": false` gives every context a row of its own.
Containers with a single thread show the thread in the session above.

Signed-off-by: Andreas Ragnerstam <andreas.ragnerstam@intel.com>
@aragners

Copy link
Copy Markdown
Contributor Author

Don't know if the README.md can be made easier to read. I proposed something. I also wonder if the configuration texts can be made more clear, but we can do that separatly, the existing are quite babbly before as well. I saw something while debugging, a frame with unknown address, I'll IM about that.

The last push was an updated README.md. Should be easier to read and more correct than your suggestion.

@aragners
aragners requested a review from clillies November 17, 2026 12:13
@aragners
aragners merged commit cccd7a3 into intel:main Nov 17, 2026
5 checks passed
@aragners
aragners deleted the call-stack-hierarchical branch November 17, 2026 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants