From: Steffen Dettmer <steffen.dettmer@googlemail.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: help with loading core files
Date: Wed, 28 Jul 2010 09:03:00 -0000 [thread overview]
Message-ID: <AANLkTi=qPD45hbjCVbTh=L0oVmZL80ZwNKfzAxJ6e9G=@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilVOGPt2T_yF-vH9s3xAsFridRw70VvZ2PWnp7n@mail.gmail.com>
On Thu, Jul 22, 2010 at 7:55 PM, Mathew Yeates <mat.yeates@gmail.com> 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.
I usually write a mock called by a automated unit test and run it
in gdb with full debug log messages enabled.
If the first run does not reveal enough information (e.g. uhh,
what was in variable x at this and that point?), it is a good
opportunity to improve the log messages.
When using an appropriate mock, it can be simple to call the
problematic function again, even from gdb (e.g. `print myFunc()').
oki,
Steffen
prev parent reply other threads:[~2010-07-28 9:03 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
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 [this message]
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='AANLkTi=qPD45hbjCVbTh=L0oVmZL80ZwNKfzAxJ6e9G=@mail.gmail.com' \
--to=steffen.dettmer@googlemail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).