Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: gdb@sourceware.org
Subject: A question about gdb script
Date: Wed, 25 Nov 2009 19:19:00 -0000	[thread overview]
Message-ID: <daef60380911250042o45462083xf478c0b384f79715@mail.gmail.com> (raw)

Hi guys,

I got a trouble in line:
 /* Make sure there is at least one LWP that has been resumed.  */
 gdb_assert (iterate_over_lwps (ptid, resumed_callback, NULL));

I set a breakpoint in the begin of this function and add commands:
silent
record
c
to it.

And set a bp in the end of this function and add commands:
silent
record stop
c
to it.

And I set a bp in internal_error.

Then I found the bug.

But I found that still have 2 ways not very easy to implement. I know
nothing about it.  could you help me with it?

1. If I want get the gdb_record.xxx file of each record cycle.  It's
still hard to me.  Because if I add "record save" to commands, each
time it will save record entry to same file.
Does gdb have some way to handle it? like:
$a=1
record save $a
$a++

2.  Sometime, I want just record a function, I want:
b functon_name
commands
silent
record
finish
#Maybe we can record save in this line, this is first question.
record stop
end
But when I really do it.  I found that gdb stop running after finish.

Could you help me with them?


Thanks,
Hui


             reply	other threads:[~2009-11-25  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 19:19 Hui Zhu [this message]
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
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=daef60380911250042o45462083xf478c0b384f79715@mail.gmail.com \
    --to=teawater@gmail.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