From: Zhiyong <zhiyong.wang@gmail.com>
To: gdb@sourceware.org
Subject: Re: Integrate BLCR to GDB
Date: Mon, 06 Apr 2009 21:47:00 -0000 [thread overview]
Message-ID: <22917611.post@talk.nabble.com> (raw)
In-Reply-To: <49DA5F4F.9070007@vmware.com>
Michael Snyder-6 wrote:
>
>
> Sounds like a very interesting project.
>
> Would you be interested in spearheading it?
>
>
>
Hi Michael,
I am totally new to gdb so I am afraid I will need quite some help from
someone here with experience. But I am more than happy to spend some time on
it.
I am also new to BLCR. My previous short description of BLCR is
incorrect. For example BLCR does support x86, x86-64, ppc, ppc64 and ARM and
Xen dom0/domU. This recent presentation may give a more complete picture
about BLCR : https://ftg.lbl.gov/CheckpointRestart/Pubs/WTTC2008-BKK.pdf.
I see there are other approach/solutions out there to achieve similar
goals in terms of debugging: like using visualization VM or effort on
reversible debugging. In my working area, I have to deal with programs with
huge memory footprint ( > 16G ), long runtime like in days and
multi-threaded. I feel BLCR approach fits the requirement nicely. Actually I
can use BLCR as standalone for my debugging purpose. I just wish I could
easily do the checkpoint/restart inside gdb.
I probably will also contact BLCR folks to see if they already have
something done for gdb or not.
Thanks,
Zhiyong.
--
View this message in context: http://www.nabble.com/Integrate-BLCR-to-GDB-tp22891922p22917611.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-04-06 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 18:22 Zhiyong
2009-04-06 20:10 ` Michael Snyder
2009-04-06 21:47 ` Zhiyong [this message]
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=22917611.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