From: Hui Zhu <teawater@gmail.com>
To: Michael Snyder <msnyder@vmware.com>,
Pedro Alves <pedro@codesourcery.com>,
Daniel Jacobowitz <drow@false.org>,
Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: A question about gdb script
Date: Fri, 27 Nov 2009 08:05:00 -0000 [thread overview]
Message-ID: <daef60380911261825n795a91b3td98b914f4906348e@mail.gmail.com> (raw)
In-Reply-To: <4B0EC7C2.2040905@vmware.com>
Cool.
What I did is:
set $stop_recording_on_next_stop=0
set height 0
b functon_name
commands
record
set $stop_recording_on_next_stop=1
finish
end
define hook-stop
if $stop_recording_on_next_stop
set $stop_recording_on_next_stop=0
record save
record stop
c
end
end
It works very well. When we done the record name issue, I will post it to wiki.
Thanks everyone. :)
Hui
On Fri, Nov 27, 2009 at 02:24, Michael Snyder <msnyder@vmware.com> wrote:
> Hui Zhu wrote:
>
>> It looks not bad, but got a lot of:
>> ---Type <return> to continue, or q <return> to quit---q
>
> That can be fixed by saying "set height 0".
>
>> If you don't mind, I will post a patch to change each fprintf_filtered
>> in record.c to fprintf_unfiltered.
>
> No, I don't agree with that. If you do that, then user has
> no choice about pagination. "Set height" gives user a choice.
>
>
next prev parent reply other threads:[~2009-11-27 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 19:19 Hui Zhu
2009-11-26 8:30 ` Daniel Jacobowitz
2009-11-26 8:51 ` Pedro Alves
2009-11-26 15:54 ` Hui Zhu
2009-11-26 17:16 ` Marc Khouzam
2009-11-27 0:32 ` Michael Snyder
2009-11-27 8:05 ` Hui Zhu [this message]
2009-11-26 15:39 ` Michael Snyder
2009-11-26 16:01 ` Hui Zhu
2009-11-27 1:37 ` Michael Snyder
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=daef60380911261825n795a91b3td98b914f4906348e@mail.gmail.com \
--to=teawater@gmail.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.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