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

GDB automation improvements #2187

Closed
3 tasks done
empathicqubit opened this issue Feb 5, 2023 · 0 comments
Closed
3 tasks done

GDB automation improvements #2187

empathicqubit opened this issue Feb 5, 2023 · 0 comments

Comments

@empathicqubit
Copy link
Contributor

empathicqubit commented Feb 5, 2023

A couple of suggestions:

  • A command to run others whenever execution stops. Something like tracecmds command ; command ; command ; .... It would only function when trace on. The registers would appear after the user specified commands. Alternatively, don't output the registers when the user specifies tracecmds and require it to be specified explicitly.
  • To support this command, add an option to x to specify the number of bytes to return. GDB does this using regex (rough example): x\s*/(\d+)(\w)*\s+([\w\d]+), where group $0 is the whole match, group $1 is the number of elements to return, group $2 any number of format specifier characters , and group $3 is the address or symbol. I will not implement the format specifier right now. If the length is not specified, use the current default length of 128.
  • A command line option to execute commands upon startup from a file. After executing it will wait for further input from the user.

I intend to implement these today if it doesn't seem insane to you.

@empathicqubit empathicqubit changed the title GDB improvements GDB automation improvements Feb 5, 2023
@suborb suborb closed this as completed May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants