Save Breakpoints

[GoogleCodeExporter]

It would be nice if EDB could scroll by whole instructions. This is 
unfortunately difficult because instructions are variable length on x86.

Original issue reported on code.google.com by evan.teran on 3 Oct 2012 at 3:13

• Blocked on: #36

[GoogleCodeExporter]

would be nice if the breakpoint plugin could save its breakpoints into some 
sort of session file.

Original comment by evan.teran on 3 Oct 2012 at 3:16

• Changed title: Save Breakpoints

[GoogleCodeExporter]

(In reply to comment #0)
> would be nice if the breakpoint plugin could save its breakpoints into some
> sort of session file.

I think, all kind of stuff (breakpoints, found functions, bookmarks, program 
arguments and comments! ) have to be saved to ONE project (session) file.

Original comment by evan.teran on 3 Oct 2012 at 3:28

[GoogleCodeExporter]

I would suggest something similar to ollydbg's session files:

The debugger provides access to session data that will be loaded and saved 
from/to disk.
A plugin can read the whole content (for e.g. compatibility settings with other 
plugins, or reading debugger session data like ignored exceptions) but only 
write to its own section.
On shutdown the debugger saves the whole thing (maybe zipped).

Original comment by evan.teran on 3 Oct 2012 at 3:28

[GoogleCodeExporter]

Original comment by evan.teran on 3 Oct 2012 at 3:45

• Now blocked on: #36

[GoogleCodeExporter]

Original comment by evan.teran on 4 Apr 2014 at 3:43

• Added labels: Type-Enhancement