From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Re: Profiling gdb?
Date: Mon, 06 Jan 2003 14:17:00 -0000 [thread overview]
Message-ID: <3E198F51.2030209@redhat.com> (raw)
In-Reply-To: <20030105222713.GA22511@nevyn.them.org>
>
> Perhaps some other time. I do _use_ monstartup, however.
>
> This patch should address all comments from the last three times this
> came up. I chose to use monstartup/_mcleanup instead of using
> moncontrol; when someone wants to use this on a system without those
> functions, _then_ we can decide how to handle it. That's just my
> opinion though. What I've done should work for at least GNU/Linux and
> FreeBSD, and that's enough to be useful. It only comes in if you
> configure it on, anyway.
>
> It works like a charm; absolutely beautifully. Thoughts, all?
(Unfortunatly, I've also leant a few things about how profiling works
... :-().
I think the commands should always be present - conditional on the
corresponding function being present. Enabling / disabling the profiler
is orthogonal to compiling with -pg. I'm not sure about the unpublished
_moncleanup() call. Are you sure of monstartup()'s function signature
(ari doesn't like the extern declarations but there isn't a header file
:-().
I also suspect that more explict commands such as:
moncontrol on/off
monstartup [ <start> <end> ]
would be better. The person using this feature will need to know how it
is implemented anyway.
(Did Jason Molenda, have something to do with the original patch?)
Andrew
next prev parent reply other threads:[~2003-01-06 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020120210343.A22638@nevyn.them.org>
[not found] ` <3C4B8A6B.30407@cygnus.com>
2003-01-05 22:27 ` Daniel Jacobowitz
2003-01-06 4:39 ` Eli Zaretskii
2003-01-06 14:17 ` Andrew Cagney [this message]
2003-01-06 15:12 ` Daniel Jacobowitz
2003-01-06 16:04 ` Andrew Cagney
2003-01-18 3:51 ` Daniel Jacobowitz
2003-01-06 18:38 ` Eli Zaretskii
2003-01-22 23:52 ` Daniel Jacobowitz
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=3E198F51.2030209@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@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