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

Need a better way of saving Breakpoints from session to session. #27

Closed
epasveer opened this issue Feb 9, 2022 · 3 comments
Closed

Comments

@epasveer
Copy link
Owner

epasveer commented Feb 9, 2022

Seer will remember Breakpoints if the Restart button is pressed.

Look at using these commands:

save breakpoints [filename]
source [-s] [-v] filename

@epasveer
Copy link
Owner Author

epasveer commented Mar 4, 2022

May need to use this to prevent prompting for future breakpoints.

set breakpoint pending on

@epasveer
Copy link
Owner Author

epasveer commented Mar 6, 2022

I've add a "save" and "load" button on the Logs tab widget to save and load all types of breakpoints (breaks, watch, print, etc...)

I need to look at starting/restarting the executable without destroying the gdb process. I believe this will then remember breakpoints between a 'restart' and a 'run'.

@epasveer
Copy link
Owner Author

I've reworked the starting of the gdb process and loading of the executable. Now they are done only if it is needed. (When the user switches to a different program). This allows all breakpoints to be remembered between executable restarts.

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

1 participant