All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Arun Sharma <asharma@fb.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RFC] perf top and deleted binaries
Date: Mon, 9 May 2011 17:58:49 -0300	[thread overview]
Message-ID: <20110509205849.GA26156@ghostprotocols.net> (raw)
In-Reply-To: <20110509182822.GA23798@dev1756.snc6.facebook.com>

Em Mon, May 09, 2011 at 11:28:23AM -0700, Arun Sharma escreveu:
> 
> For long running binaries which may have been replaced or deleted, today 
> perf top spits out a warning and doesn't show anything. For eg:
> 
> test.c:
> 
> main()
> {
> 	while(1);
> }
> 
> gcc -O2 test.c -o test
> ./test &
> gcc -O2 test.c -o test	# overwrite the binary
> perf top -p <pid>
> 
> shows nothing. It could instead show:
> 
> 100% <unresolved>	test
> 
> like perf record/report would show for the same test case. Comments?

Agreed :-)

When/if we get build-id as first class citizen, stashing it in some
kernel data structure at DSO load time, we'll be able to use it for
content based DSO lookup in the cache.

- Arnaldo

      reply	other threads:[~2011-05-09 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 18:28 [RFC] perf top and deleted binaries Arun Sharma
2011-05-09 20:58 ` Arnaldo Carvalho de Melo [this message]

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=20110509205849.GA26156@ghostprotocols.net \
    --to=arnaldo.melo@gmail.com \
    --cc=asharma@fb.com \
    --cc=linux-perf-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.