This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/9314] Unable to checkpoint after restart


------- Additional Comments From uri at 4refs dot com  2009-01-20 19:51 -------
This is not so much a bug as it is a feature request. I think it should be
possible to implement this feature using the new Python interface but I haven't
tried yet. I can almost use a hook for this purpose:

.gdbinit:
define hookpost-restart
checkpoint
end

This hook isn't ideal though. First, it creates the checkpoint even if the
original checkpoint hasn't moved. Second, while that location in program
execution is saved through the new checkpoint, the original number moves.

.gdbinit:
define hookpost-restart-and-move
checkpoint
restart $last
end

With this behavior, the checkpoint behaves more like a CVS tag (once created it
can never be moved) than a branch.

This behavior makes more sense because in my mental model a checkpoint is a
point of execution, not a process. Using the example from the documentation,
when you bookmark a page, you are thinking of the last page you read, not page
697 because the number isn't useful to you except to find the last page you
read. This behavior would make even more sense if GDB added a new feature to
label checkpoints like variables (ie "set $packetSent = checkpoint").

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9314

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]