This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Large memory usage by gdb
- From: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>
- To: Alex Lindsay <alexlindsay239 at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Tue, 01 Aug 2017 21:11:57 +0200
- Subject: Re: Large memory usage by gdb
- Authentication-results: sourceware.org; auth=none
- Ironport-phdr: 9a23:MhUecRBfB0awxjP+ihOmUyQJP3N1i/DPJgcQr6AfoPdwSPT6pcbcNUDSrc9gkEXOFd2CrakV26yO6+jJYi8p2d65qncMcZhBBVcuqP49uEgeOvODElDxN/XwbiY3T4xoXV5h+GynYwAOQJ6tL1LdrWev4jEMBx7xKRR6JvjvGo7Vks+7y/2+94fdbghMhzexe69+IAmrpgjNq8cahpdvJLwswRXTuHtIfOpWxWJsJV2Nmhv3+9m98p1+/SlOovwt78FPX7n0cKQ+VrxYES8pM3sp683xtBnMVhWA630BWWgLiBVIAgzF7BbnXpfttybxq+Rw1DWGMcDwULs5Qiqp4bt1RxD0iScHLz85/3/Risxsl6JQvRatqwViz4LIfI2ZMfxzdb7fc9wHX2pMRsVfWTFBDI2iYYUADeQBMvpfoYbyqFUDtge+CAu2Ce/z0DJEmn370Ksn2OohCwHG2wkgEsoUvnTUrdX1MKYSUfitzKbW0D7Mb+lZ2S366IjRbxAhoO+DXahrccHMzkQvDwPFjlSUqYzkJzOVzvoCv3KV7uV6T+KvjHcnqxxwojex3McskZLEhpkWylHE8yV23po1KcejR0FleNOpFoZbuSKCN4ZuQc4uXntktDg1x7AEo5K3YSYHxZc9yxPRa/GKdZWD7Aj5W+aLOzh4gWpoeLe4hxmv70et0vb8Vsyo0FZSqSpFj8XMumgN1xPN7siHTeNw/kK81jqX1gDT7P9LIVwsmKfYNpIt2KA8m5URvEjZAyP7lkb7gLWYe0gk4uSo7v7oYrTipp+SLY90jQT+P7w2msy/AOQ4NgkOX3CD+euizrHi81f2QK9Njv0vj6nZsY7VJd4ApqOiGA9V0YYi6xChADe6ytgXhmcIIEpfeB2bl4jpJ03OIPfgAPilh1Sjjjhqx/THPr3nH5rNNWLMkbf/cbtz70NR0wUzzdVF6JJVDrENOu78Wkj0tI+QMhhsGgi5067DCdNxzYoPETaGBqKJNKLUvUSB97h0csGDYYYUvHD2LP1ztND0inpsoV8ceaixxZZfV3miGe17IkiDejK4mtcAFWYSpgd4U+Xwj0SfUDNJfF6pXLM66y19Ao/wXtSLfZyknLHUhHTzJZZRfG0TTwnUSXo=
- References: <8d511930-9914-9aef-363f-2fff37dfc6a8@gmail.com> <1501014538.2145.22.camel@skynet.be> <832a7365-8905-a49e-b97d-2d8a3520c747@gmail.com>
On Mon, 2017-07-31 at 17:11 -0500, Alex Lindsay wrote:
> Philippe,
>
> Is memcheck a better tool to use here compared to massif?
In valgrind 3.13, memcheck provides a quite detailed/precise
way to see delta memory increase/decrease.
Typically, you will give --xtree-memory=full argument,
and then e.g. use vgdb to launch a (delta) leak search
after each run.
You can then use kcachegrind to visualise the resulting
memory increase.
Massif is IMO less precise, but automatically produces
memory status at regular interval.
So, in summary, I would use valgrind 3.13 and memcheck
(with an additional benefit that if ever your use case
causes real memory leaks, memcheck will detect them).
Philippe
>
> Alex
>
> On 07/25/2017 03:28 PM, Philippe Waroquiers wrote:
> > Run gdb under Valgrind, and make some heap profiling dump at regular
> > interval, (e.g. after each run).
> >
> > With valgrind 3.12 or before, you can do a leak report to show
> > the delta (increase or decrease) compared to the previous leak search,
> > including the reachable blocks. So, you will be able to see what
> > increases the memory.
> >
> > If you compile the latest Valgrind (3.13), you can e.g. use memcheck
> > and produce heap profiling reports readable with kcachegrind.
> >
> > You will need a gdb compiled with debug or install the debug info
> > of gdb to have understandable stack traces.
> >
> > Philippe
> >
> > On Tue, 2017-07-25 at 15:20 -0500, Alex Lindsay wrote:
> >> My OS is Ubuntu 17.04. Using both gdb 7.12 and 8.0, I experience large
> >> memory usage when debugging my executable. As I add breakpoints and run
> >> the executable multiple times in a single session, memory usage grows
> >> continuously, regularly hitting 10s of GBs. I don't recall experiencing
> >> this issue with earlier Ubuntu versions (and also likely earlier
> >> versions of gdb). When I debug the same executable with `lldb`, memory
> >> usage is pretty much constant at around 2 GB. Does anyone have any
> >> suggestions?
> >>
> >> Alex
> >
>