From: Zhiyong <zhiyong.wang@gmail.com>
To: gdb@sourceware.org
Subject: Integrate BLCR to GDB
Date: Sun, 05 Apr 2009 18:22:00 -0000 [thread overview]
Message-ID: <22891922.post@talk.nabble.com> (raw)
Hi,
If my understanding is correct, current gdb checkpoint/restart is using
fork() and does not support multi-threading.
I am interested to know if someone has done some work to integrate BLCR
(Berkely Lab Checkpoint/Restart ,
https://ftg.lbl.gov/CheckpointRestart/CheckpointRestart.shtml) into gdb?
As a standalone, BLCR is quite helpful in certain debugging scenarios. But
it is a bit hard to use with gdb , i.e. breakpoints can not be saved and
restart is not convienent to stop at certain point etc.
BLCR's limitation is it is only for Linux x86 and x86_64. It also needs to
load kernel modules which may or may not be an issue. It is not targeting
debugging but rather process management/fault tolerance.
Thanks,
Zhiyong
--
View this message in context: http://www.nabble.com/Integrate-BLCR-to-GDB-tp22891922p22891922.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next reply other threads:[~2009-04-05 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 18:22 Zhiyong [this message]
2009-04-06 20:10 ` Michael Snyder
2009-04-06 21:47 ` Zhiyong
2009-04-06 22:35 ` Michael Snyder
2009-04-06 22:45 ` Thiago Jung Bauermann
2009-04-06 23:37 ` Zhiyong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22891922.post@talk.nabble.com \
--to=zhiyong.wang@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox