Konloch / Konloch/bytecode-viewer
Stacktrace analysis
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 15.6k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
What would be a pretty useful feature is a way to input a stacktrace, and then make BCV automatically load the class where the exception happens, open the bytecode disassembler, go to the line and highlight where the exception took place. I often need to do this manually, and it would be great if it was automated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the existing class-loading, bytecode-disassembler navigation, and exception-handling entry points; done means a stacktrace can be entered and BCV opens the relevant class, navigates to the indicated line, and highlights the exception location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100