From: Nikola Valerjev <nikola@ghs.com>
To: sid@sources.redhat.com
Subject: gprof store and reset pins
Date: Fri, 17 Oct 2003 19:41:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.96.1031017120057.12176B-100000@pong.ghs.com> (raw)
Hi,
I've been trying to use gdb and gprof components in 'sid' to get the profiling
information out. The problem is that by default (i.e. options --gdb=PORT and
--gprof=FILE) will dump the information to gmon.out only once gdb disconnects
from the target. That happens because of the following default configuration:
connect-pin shutdown-seq output-7 -> mm_A-0/gprof store
What I would like to do is get gmon.out dumped while still being connected.
Also I would like to have some way of reseting the gprof info (driving the
'reset' pin) on demand (presumably using the 'gdb' component or the
'io-socket' component - but not necessarily using the 'gdb' debugger). That
would have the benefit of being able to collect the profiling data only for one
section of the code - not for the entire program.
For the first problem, I changed the configuration file to say
connect-pin yield-net output-0 -> mm_A-0/gprof store
(yield-net input is driven by 'gdb' yield). So that has the effect of dumping
gmon.out whenever the target process stops. It is not demand driven, and it
probably dumps it more often than I want, but it is good enough for now.
However, I can't figure out which output pin to use to drive 'gprof reset'
command. One option was to do
connect-pin shutdown-seq output-7 -> mm_A-0/gprof reset
but then I get a reset only after I disconnect from 'sid'. What I really need
is some way of reseting it while still being connected.
I would appreciate any help with this.
Thanks
Nikola Valerjev
Green Hills Software
next reply other threads:[~2003-10-17 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 19:41 Nikola Valerjev [this message]
2003-10-18 10:08 ` Frank Ch. Eigler
2003-10-21 0:14 ` Nikola Valerjev
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=Pine.SOL.3.96.1031017120057.12176B-100000@pong.ghs.com \
--to=nikola@ghs.com \
--cc=sid@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).