public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: sprofil() implementation
Date: Wed, 21 Mar 2001 22:00:27 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005328@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005326@msgid-missing>

>>>>> On 21 Mar 2001 12:17:30 -0800, Ulrich Drepper <drepper@redhat.com> said:

  Uli> David Mosberger <davidm@hpl.hp.com> writes:
  >> Attached below is an implementation of the sprofil() call.

  Uli> Thanks, I've added the patch.  There was one bug left (on 32-bit
  Uli> archs) and I did some reformatting but essentially it is plainly
  Uli> accepted.  Thanks.

Thanks!

  Uli> But one word of warning: this interface is insufficient.  We need a
  Uli> way to dynamically add and remove new segments.  This is necessary to
  Uli> support dlopen() etc.

Yes, I considered that.  I thought it would be OK to use sprofil() to
stop profiling completely on a dlopen(), register the new library, and
then call sprofil() again.  Apart from being a bit slower than
strictly necessary, I don't think there is an issue with this.  Are
you concerned about performance or something else?

On a related topic: the gmon.out file currently does not encode any
filenames.  That's would create problems with dlopen().  I think the
best way to fix this is to add a new gmon.out tag that encodes the
filename to which the remainder of the file applies
(GMON_TAG_IMAGE_PATH or something like that).

	--david


  reply	other threads:[~2001-03-21 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 20:17 [Linux-ia64] Re: sprofil() implementation Ulrich Drepper
2001-03-21 22:00 ` David Mosberger [this message]
2001-03-22  1:13 ` Ulrich Drepper

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=marc-linux-ia64-105590693005328@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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