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

Next steps of the remaining work of debugging support on ARM64 #1770

Closed
hengwu0 opened this issue Nov 26, 2019 · 5 comments
Closed

Next steps of the remaining work of debugging support on ARM64 #1770

hengwu0 opened this issue Nov 26, 2019 · 5 comments

Comments

@hengwu0
Copy link
Contributor

hengwu0 commented Nov 26, 2019

1、There is bug in orig-Detach function, it needs to be investigated to fix TestExit and TestExitAfterContinue.
2、TestDisassembleGlobalVars needs to be investigated. The disasm has been implemented and all other disasm tests passed, except this one. It seems can't find main.v in range of mainfn.Entry and mainfn.End on arm64.
3、To implemente stacktrace with separate amd64-arch code again.
4、To implemente Fp registers and Fp instructions

#1733, #118

@hengwu0
Copy link
Contributor Author

hengwu0 commented Nov 28, 2019

1、There is bug in orig-Detach function, it needs to be investigated to fix TestExit and TestExitAfterContinue.

fixed by eb6d01a b951551.

@hengwu0
Copy link
Contributor Author

hengwu0 commented Nov 29, 2019

2、TestDisassembleGlobalVars needs to be investigated. The disasm has been implemented and all other disasm tests passed, except this one. It seems can't find main.v in range of mainfn.Entry and mainfn.End on arm64.

traced in #1778

@hengwu0
Copy link
Contributor Author

hengwu0 commented Nov 29, 2019

3、To implemente stacktrace with separate amd64-arch code again.

traced in #1780

@hengwu0
Copy link
Contributor Author

hengwu0 commented Oct 14, 2020

4、To implemente Fp registers and Fp instructions

The Fp registers and Fp instructions can be got correctly in delve already, but it seems that the floating-point registers are displayed in wrong format and hardly read when debugging. which traced in #2198

@hengwu0
Copy link
Contributor Author

hengwu0 commented Sep 23, 2022

I closed this issue, since all lists are done.

@hengwu0 hengwu0 closed this as completed Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants