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

[Bug] gef.autosave_breakpoints_file was removed #965

Closed
1 of 9 tasks
Summon528 opened this issue Jul 17, 2023 · 0 comments · Fixed by #969
Closed
1 of 9 tasks

[Bug] gef.autosave_breakpoints_file was removed #965

Summon528 opened this issue Jul 17, 2023 · 0 comments · Fixed by #969

Comments

@Summon528
Copy link

GEF+GDB version

GEF: (Standalone)
Blob Hash(/home/xxx/.gef-a85368fc771dcbb4db2b41818781e182845015b9.py): 1a409c397646df9c0b8549d576cd7c7f8ec1ef47
SHA256(/home/xxx/.gef-a85368fc771dcbb4db2b41818781e182845015b9.py): f096ff3bf50df08dbbc698a919360014f86f1eea315011cdabebd72a30a5bce8
GDB: 13.2
GDB-Python: 3.11

Operating System

openSUSE Tumbleweed

Describe the issue you encountered

gef.autosave_breakpoints_file doesn't seem to save breakpoints file.

Do you read the docs and look at previously closed issues/PRs for similar cases?

No

Architecture impacted

  • X86
  • X64
  • ARM
  • ARM64
  • MIPS
  • MIPS64
  • PPC
  • PPC64
  • RISCV

Describe your issue. Without a proper reproduction step-by-step, your issue will be ignored.

  1. In .gef.rc set autosave_breakpoints_file = /home/xxx/bps
  2. Start gdb, add some breakpoints, quit
  3. No file is created

Minimalist test case

No response

Additional context?

Looks like the code was removed in #839. The define hook-quit does not exist in the current code base anymore and I don't see any replacement code unless I'm missing something.

@hugsy hugsy changed the title [Bug] [Bug] gef.autosave_breakpoints_file was removed Jul 17, 2023
@hugsy hugsy self-assigned this Jul 17, 2023
hugsy pushed a commit that referenced this issue Jul 21, 2023
@hugsy hugsy added this to the 2023.08 milestone Jul 21, 2023
hugsy added a commit that referenced this issue Jul 22, 2023
* Fixes #965

* Also changes the dates 2022 -> 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants