Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add interactive window for analyzing stack traces #76

Open
edjubuh opened this issue Feb 18, 2019 · 1 comment
Open

Add interactive window for analyzing stack traces #76

edjubuh opened this issue Feb 18, 2019 · 1 comment
Assignees
Labels
feature A brand new feature in progress This is currently being worked on p: high High priority
Milestone

Comments

@edjubuh
Copy link
Member

edjubuh commented Feb 18, 2019

As part of purduesigbots/pros#112, we need to have a way to paste a stack trace and see what lines they come from. This would involve parsing the output of the data abort (some amount), ideally be able to check that the binary running on the V5 is consistent with the local one, and use addr2line and objdump to display something more digestible than PC addresses.

@edjubuh edjubuh added this to the 3.1.5 milestone Feb 18, 2019
@HotelCalifornia HotelCalifornia added feature A brand new feature in progress This is currently being worked on p: normal Normal priority labels Mar 13, 2019
@omegaStag omegaStag added p: high High priority and removed p: normal Normal priority labels Sep 6, 2022
@BennyBot
Copy link
Member

Just an update to this issue, this issue will not need to be an interactive window. Preferably, it can output the digestible output to the screen and a txt file in the project folder and VSCode will be able to parse that file to jump the user to where the code went wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A brand new feature in progress This is currently being worked on p: high High priority
Projects
None yet
Development

No branches or pull requests

4 participants