Skip to content

Add new tool: Callstack Analyzer#121

Open
BenCrafterRED wants to merge 2 commits intorarsm:masterfrom
BenCrafterRED:master
Open

Add new tool: Callstack Analyzer#121
BenCrafterRED wants to merge 2 commits intorarsm:masterfrom
BenCrafterRED:master

Conversation

@BenCrafterRED
Copy link

I developed a tool to help analyze the call stack of a running program inside RARS at the Univerity of Applied Sciences Zwickau. The intent is that this tool may be used by others to help explain and understand the call stack.

Features

  • Choose between different strategies used to recognize different stack frames.
  • Compare the results of different strategies.
  • Live log of all events regarding call, return, and stack access.
  • Dynamic stack diagram including:
    • Visual stack pointer and frame pointer
    • Name of the called symbol corresponding to a frame.
    • Resolution of return addresses to symbol names

Screenshot

Screenshot_20260121_115455

NOTE: I have used Java 21 and the rest of the code worked just fine. If this were a problem, I could rewrite the Callstack Analyzer to use Java 11 only. However, I would prefer to use Java 21 as this would involve quite a bit additional work.

@ladyslipper-glade
Copy link

ladyslipper-glade commented Jan 27, 2026

To what extent would changing to Java 21 cause hardship for the user community, some of whom might be "stuck" on an older version of Java for reasons outside their control? I don't have an answer to this question. Personally, I think moving to Java 21 sounds fine, but I can appreciate how it might be problematic.

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.

2 participants