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.

Sign up for GitHub

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

Unable to stepi after stop in gdb breakpoint #6

Open
mickael-guene opened this issue Sep 22, 2016 · 2 comments
Open

Unable to stepi after stop in gdb breakpoint #6

mickael-guene opened this issue Sep 22, 2016 · 2 comments
Labels
arm64 bug workaround

Comments

@mickael-guene
Copy link
Owner

When debugging a program using gdb. If you are stop on a breakpoint then you can't stepi. You have to disable or delete breakpoint to go further.
This was verify on docker arm64 image.
@mickael-guene
Copy link
Owner Author

works for mickaelguene/arm64-debian-dev:jessie but not mickaelguene/arm64-debian-dev:testing

@mickael-guene mickael-guene reopened this Oct 28, 2016
@mickael-guene
Copy link
Owner Author

mickael-guene commented Aug 21, 2017 •
edited
Loading

After more investigation, it appears that this problem is due to gdb displaced stepping feature. Unfortunately to work this feature need to update pc using PTRACE_SETREGSET ptrace command, but under umeq it's not possible to update pc using this command for the moment.
The good news is that there is a very easy workaround, just disable gdb displaced stepping !!! To disable it just use following command under gdb:

set displaced-stepping 0

In the long term fixing this problem means I have to support pc changes in PTRACE_SETREGSET ptrace command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
arm64 bug workaround
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mickael-guene