Re: How to diagnose memory leak in kvm-qemu-0.14.0?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 19, 2011 at 9:40 AM, Stefan Hajnoczi <stefanha@xxxxxxxxx> wrote:
> On Wed, May 18, 2011 at 5:44 PM, Steve Kemp <steve@xxxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux