The Wayback Machine - https://web.archive.org/web/20200705040047/https://github.com/cs01/gdbgui/issues/264
Skip to content

/ gdbgui

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

Jump to bottom

Debugging ARM code shows instructions incorrectly #264

Open
sherrellbc opened this issue Mar 9, 2019 · 1 comment
Open

Debugging ARM code shows instructions incorrectly #264

sherrellbc opened this issue Mar 9, 2019 · 1 comment

Comments

@sherrellbc
Copy link

@sherrellbc sherrellbc commented Mar 9, 2019 •
edited

Describe the bug
I was just giving it a shot on ARM (remote debugging) and noticed a few things. The height of the rows for in the register view make it so that you can only see about 15 registers at once. Could that be scaled back/down? Also, the instructions shown in the debug window are a bit munged together.

The first instruction shown in the screenshot is msr x0, ttbr0_el3. But what is shown in the gdbgui window is mrstx0, ttbr0_el3. It's thrown together the mrs and the x0 while also putting a random t in the mix.

To Reproduce
Debug baremetal/kernel ARM code. The instruction display issue might be present on any ARM code, but certainly the use of MSRs (as shown) is not.

Screenshots
https://imgur.com/a/wU9I4PZ

Please complete the following information:

  • OS: OSX
  • gdbgui version (gdbgui -v): 0.13.1.1
  • gdb version (gdb -v): 8.2.1
  • browser [e.g. chrome, safari]: Chrome
  • python packages (pip freeze):
@Swiftloke
Copy link

@Swiftloke Swiftloke commented Apr 20, 2019 •
edited

I'd like to draw a little more attention to this, as I'm running into it as well. When debugging some code on the Nintendo 3DS (using a patched arm-none-eabi-gdb provided by devkitARM, version 8.0) the code that appears in the browser window looks a little something like this: https://imgur.com/TD9Jhjz
Could this perhaps have something to do with a failure to properly interpret \t? If pointed in the right direction, I might be able to poke around for the bug a bit.
Also note that this issue occurs on 32-bit ARM as well (OP is debugging Aarch64).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
@sherrellbc @Swiftloke
You can’t perform that action at this time.