From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129508 invoked by alias); 7 Aug 2017 18:19:17 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 129475 invoked by uid 89); 7 Aug 2017 18:19:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=HX-Envelope-From:sk:philipp, menus, analyse, wasted X-HELO: mailsec104.isp.belgacom.be Received: from mailsec104.isp.belgacom.be (HELO mailsec104.isp.belgacom.be) (195.238.20.100) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 07 Aug 2017 18:19:08 +0000 IronPort-PHdr: =?us-ascii?q?9a23=3A6R1FVxKZm+ws6V4dB9mcpTZWNBhigK39O0sv0rFi?= =?us-ascii?q?tYgeK/7xwZ3uMQTl6Ol3ixeRBMOAuqIC07KempujcFRI2YyGvnEGfc4EfD4+ou?= =?us-ascii?q?JSoTYdBtWYA1bwNv/gYn9yNs1DUFh44yPzahANS47xaFLIv3K98yMZFAnhOgpp?= =?us-ascii?q?POT1HZPZg9iq2+yo9ZDeZwZFiCChbb9uMR67sRjfus4KjIV4N60/0AHJonxGe+?= =?us-ascii?q?RXwWNnO1eelAvi68mz4ZBu7T1et+ou+MBcX6r6eb84TaFDAzQ9L281/szrugLd?= =?us-ascii?q?QgaJ+3ART38ZkhtMAwjC8RH6QpL8uTb0u+ZhxCWXO9D9QKsqUjq+8ahkVB7oiD?= =?us-ascii?q?8GNzEn9mHXltdwh79frB64uhBz35LYbISTOfFjfK3SYMkaSHJCUMhMVyJPHI2y?= =?us-ascii?q?YIkBD+UdOuhXoIbzqkASrRa8HwSgGPnixiNKi3LwwKY00/4hEQbD3AE4BdwOsH?= =?us-ascii?q?XUrNH0NKcKSeC60rTDwjXZYPNM3jf98ZXIchE/rvGWRrJ7bM3cyVEvFwPEilWQ?= =?us-ascii?q?qJTlPyuL2egXvWmU9fBgVeW2i246qgF+vCKvxtw3h4nShYIUylbE+jtlwIovPt?= =?us-ascii?q?K3Vld2bNi5G5VTryGXL4h7Tt44T212tys3yKcKtYO1cSUJ0pgqyR7SZvqaeIaS?= =?us-ascii?q?+B3jTvyeITJgiXJgf7Kwmgi9/FC7yu35Ssm0yFFKrjdZktXUtnACyRjT6s+fR/?= =?us-ascii?q?t440itwTeP1wbN5eFYOU05lrfXJ4Q/zrM/lJcfq1nPEyH1lUnsgqKbdl0o+u2y?= =?us-ascii?q?5OTmZrXmqIWcN4hxigzmKqQums2/AeA5MggWR2iU5/6w1bP58k3jR7VKl+A2kq?= =?us-ascii?q?jHv5DAPsQWvbW5AwxV04Yl9Rm/Ey2q388GknUfNlJKZAqHj5T1O1HJOP33F/O/?= =?us-ascii?q?jEqjkTdvxvDGOKDuAo7XIXnDjrvsc7Jw5lVTyAo2199f5pZUBqsdL/L0X0+i/O?= =?us-ascii?q?DfWzY9Phz85+fhBM50x8tKUGaCEquYNq/JuE7SvbMHLOyFZYtTszH4fasL/fnr?= =?us-ascii?q?2Ec5mFscZbGklaQecnehA/VrOV7RNWLsg9MACX8H+BU3VuvzlVyPSyV7fHWjWa?= =?us-ascii?q?8goDs2XtH1RbzfT5yg1eTSlBywGYdbMyUfUgiB?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2BJBQBjrohZ/yOK91FcHAEBBAEBCgEBF?= =?us-ascii?q?gEBAQMBAQEJAQEBgy+FI4pkc5EALwGVZQ6CBIVHAoRaQBgBAQEBAQEBAQEBAWo?= =?us-ascii?q?oQgEBAwkCgWEkAYJAAQEBAQIBIwQvIwULCAMYAgImAgI5HgaKOgyrIIEjgWw6i?= =?us-ascii?q?00BAQgCJoELgh2DToUKhDgUgzqCYQWgD4IokguSTJYIHziBCnRhhRQfgWk+hTO?= =?us-ascii?q?BX0+CQQEBAQ?= X-IPAS-Result: =?us-ascii?q?A2BJBQBjrohZ/yOK91FcHAEBBAEBCgEBFgEBAQMBAQEJAQE?= =?us-ascii?q?Bgy+FI4pkc5EALwGVZQ6CBIVHAoRaQBgBAQEBAQEBAQEBAWooQgEBAwkCgWEkA?= =?us-ascii?q?YJAAQEBAQIBIwQvIwULCAMYAgImAgI5HgaKOgyrIIEjgWw6i00BAQgCJoELgh2?= =?us-ascii?q?DToUKhDgUgzqCYQWgD4IokguSTJYIHziBCnRhhRQfgWk+hTOBX0+CQQEBAQ?= Received: from 35.138-247-81.adsl-dyn.isp.belgacom.be (HELO md) ([81.247.138.35]) by relay.skynet.be with ESMTP/TLS/AES128-GCM-SHA256; 07 Aug 2017 20:19:05 +0200 Message-ID: <1502129972.1467.13.camel@skynet.be> Subject: Re: Large memory usage by gdb From: Philippe Waroquiers To: Alex Lindsay Cc: gdb@sourceware.org Date: Mon, 07 Aug 2017 18:19:00 -0000 In-Reply-To: <420b109c-1610-d687-ae9a-b172542fafca@gmail.com> References: <8d511930-9914-9aef-363f-2fff37dfc6a8@gmail.com> <1501014538.2145.22.camel@skynet.be> <832a7365-8905-a49e-b97d-2d8a3520c747@gmail.com> <1501614717.1461.3.camel@skynet.be> <420b109c-1610-d687-ae9a-b172542fafca@gmail.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-08/txt/msg00014.txt.bz2 On Fri, 2017-08-04 at 16:14 -0500, Alex Lindsay wrote: > So I wanted to share what I've been doing to make sure that I'm not > wasting my time (or the list's). For sure, fixing leaks is not wasted time. > Since this is my first deep dive into valgrind, I started "simple". > I've been running more or less: > valgrind --xtree-leak=yes gdb --args ./hello If you are only interested in leaks (definite and/or possible leaks) and you do not have zillions of different leaks, then using the classical text output for leak search might be easier. If you use kcachegrind to visualise xtree leak reports, you might have to tune the way the graph is shown by using menus in the graph such as: right click -> Graph -> Caller Depth -> ... -> Callee Depth -> ... -> Min Node Cost -> ... Once the leaks are solved, then to visualise the increase of memory caused by a run in gdb, you might do (from a shell) : vgdb leak_check xtleak kinds all any In kcachegrind, you can then analyse various 'events' (typically for your case, you might look first at 'increase Reachable Bytes' Alternatively, to see memory increase in a textual output, you might do: vgdb leak_check full kinds all increased (if output too large, you can add limited 100 after increased to output only the 100 (or whatever nr) 'biggest increase'. Philippe