This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb cannot call help function in replay mode
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: jian shen <vicshen at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Wed, 26 Jun 2013 20:45:18 +0200
- Subject: Re: gdb cannot call help function in replay mode
- References: <CAC5CAUrgKcRcm_WnJigB5UNrDFqnpQhqmh_b+hUj3t-sz1pqGw at mail dot gmail dot 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