From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: jian shen <vicshen@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb cannot call help function in replay mode
Date: Wed, 26 Jun 2013 18:45:00 -0000 [thread overview]
Message-ID: <20130626184518.GA3080@host2.jankratochvil.net> (raw)
In-Reply-To: <CAC5CAUrgKcRcm_WnJigB5UNrDFqnpQhqmh_b+hUj3t-sz1pqGw@mail.gmail.com>
On Tue, 25 Jun 2013 06:11:26 +0200, jian shen wrote:
> In below example, when I try to call function getA1() in replay mode, gdb give
> warning that it will write memory and make the execution log unusable, although
> this function does not write memory, only read memory.
The function writes to stack and registers.
> In real project, I have some helper function to dump what a handle is. But in
> replay mode, I could not call such functions. This limitation makes the replay
> mode almost unusable to me. Any suggestion?
You should use Python Pretty Printer instead. This will also work for core
file analysis where you also cannot call inferior functions.
Jan
next prev parent reply other threads:[~2013-06-26 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 4:11 jian shen
2013-06-26 18:45 ` Jan Kratochvil [this message]
2013-06-27 1:48 ` jian shen
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=20130626184518.GA3080@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=vicshen@gmail.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