From: Mathew Yeates <mat.yeates@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: help with loading core files
Date: Thu, 22 Jul 2010 18:14:00 -0000 [thread overview]
Message-ID: <AANLkTilIQH5N3VkD2oEsFNnTzOVMP4lCyLquupljvoF-@mail.gmail.com> (raw)
In-Reply-To: <4C488940.8020503@vmware.com>
yeah, I was just looking at "checkpoint". It seems to me that if gdb
is able to create checkpoints, it should also be able to do what I
want (restart and immediately go to a certain location)
On Thu, Jul 22, 2010 at 11:09 AM, Michael Snyder <msnyder@vmware.com> wrote:
> Jan Kratochvil wrote:
>>
>> On Thu, 22 Jul 2010 19:55:03 +0200, Mathew Yeates wrote:
>>>
>>> How do people deal with running to a breakpoint that takes 10 minutes
>>> to get to? It would be great if I could run to the breakpoint once,
>>> save some info, and in the future just return to the breakpoint and
>>> keep running from there.
>>
>> See info '(gdb)Checkpoint/Restart' but it does not work with threads and
>> it is
>> not a commonly used feature (at least I have never used it myself).
>
> Jan, I think he wants to quit his gdb session and return to it.
> Checkpoints aren't preserved across quitting and restarting gdb.
>
next prev parent reply other threads:[~2010-07-22 18:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 17:04 Mathew Yeates
2010-07-22 17:07 ` Michael Snyder
2010-07-22 17:16 ` Mathew Yeates
2010-07-22 17:26 ` Michael Snyder
2010-07-22 17:28 ` Mathew Yeates
2010-07-22 17:29 ` Michael Snyder
2010-07-22 17:55 ` Mathew Yeates
2010-07-22 18:07 ` Jan Kratochvil
2010-07-22 18:09 ` Michael Snyder
2010-07-22 18:14 ` Mathew Yeates [this message]
2010-07-22 18:18 ` Jan Kratochvil
2010-07-28 9:06 ` Steffen Dettmer
2010-07-28 12:24 ` Jan Kratochvil
2010-07-28 9:03 ` Steffen Dettmer
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=AANLkTilIQH5N3VkD2oEsFNnTzOVMP4lCyLquupljvoF-@mail.gmail.com \
--to=mat.yeates@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=msnyder@vmware.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).