All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Steve Kemp <steve@bytemark.co.uk>
Cc: kvm@vger.kernel.org
Subject: Re: How to diagnose memory leak in kvm-qemu-0.14.0?
Date: Thu, 19 May 2011 09:50:51 +0100	[thread overview]
Message-ID: <BANLkTikhFhnzc2+gZFYpi=ZXZppr1_iQfQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimq2S3a=BbDJvxkeET9pK64ybKEiw@mail.gmail.com>

On Thu, May 19, 2011 at 9:40 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Wed, May 18, 2011 at 5:44 PM, Steve Kemp <steve@bytemark.co.uk> wrote:
> If you have SystemTap installed you may wish to use the "dtrace"
> backend instead of "simple".  You can then use SystemTap scripts on
> the probes.  SystemTap is more powerful, it should allow you to
> extract call stacks when probes are fired but I'm not experienced with
> it.

Forgot to add that the __builtin_return_address() gcc extension can be
used to collect return addresses even with the simple trace backend:
http://gcc.gnu.org/onlinedocs/gcc-4.4.2/gcc/Return-Address.html#index-g_t_005f_005fbuiltin_005freturn_005faddress-2431

I've used it in the past as a poor man's stack trace when tracking
down memory leaks.

Stefan

  reply	other threads:[~2011-05-19  8:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 16:44 How to diagnose memory leak in kvm-qemu-0.14.0? Steve Kemp
2011-05-19  8:40 ` Stefan Hajnoczi
2011-05-19  8:50   ` Stefan Hajnoczi [this message]
2011-05-19 11:00   ` Steve Kemp
2011-05-19 11:57   ` Steve Kemp
2011-05-20 11:01     ` Stefan Hajnoczi
2011-05-20 11:47       ` Steve Kemp
2011-05-20 13:16         ` Stefan Hajnoczi
2011-05-20 13:47           ` Steve Kemp
2011-05-20 14:32             ` Stefan Hajnoczi
2011-05-20 14:52               ` Steve Kemp

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='BANLkTikhFhnzc2+gZFYpi=ZXZppr1_iQfQ@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=steve@bytemark.co.uk \
    /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.