Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Alex Lindsay <alexlindsay239@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Large memory usage by gdb
Date: Wed, 26 Jul 2017 07:28:00 -0000	[thread overview]
Message-ID: <86bmo7pshw.fsf@gmail.com> (raw)
In-Reply-To: <8d511930-9914-9aef-363f-2fff37dfc6a8@gmail.com> (Alex Lindsay's	message of "Tue, 25 Jul 2017 15:20:25 -0500")

Alex Lindsay <alexlindsay239@gmail.com> writes:

> 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?

What is your executable?  Can you give us some characteristics of your
executable to help us to reproduce this problem?  Is it multi-threaded
program?  Is it a C or C++ program?  Does it load many shared library?

-- 
Yao (齐尧)


  parent reply	other threads:[~2017-07-26  7:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 20:20 Alex Lindsay
2017-07-25 20:28 ` Philippe Waroquiers
2017-07-31 22:11   ` Alex Lindsay
2017-08-01 19:12     ` Philippe Waroquiers
     [not found]       ` <420b109c-1610-d687-ae9a-b172542fafca@gmail.com>
2017-08-04 21:43         ` Alex Lindsay
2017-08-07  9:16           ` Yao Qi
2017-08-07 19:53             ` Philippe Waroquiers
2017-08-07 21:04               ` Alex Lindsay
2017-08-07 21:34                 ` Simon Marchi
2017-08-07 18:19         ` Philippe Waroquiers
2017-07-26  7:28 ` Yao Qi [this message]
     [not found]   ` <4fc14853-b066-4fd7-f0c9-b98f442a9a95@gmail.com>
2017-07-26 15:55     ` Yao Qi

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=86bmo7pshw.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=alexlindsay239@gmail.com \
    --cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox