public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "szotsaki at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/18590] GDB memory leak (5+ GB) with Qt Creator in python theDumper.showData
Date: Wed, 24 Jun 2015 11:17:00 -0000	[thread overview]
Message-ID: <bug-18590-4717-ZDjyPnr48u@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18590-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18590

--- Comment #1 from Ákos Szőts <szotsaki at gmail dot com> ---
Created attachment 8387
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8387&action=edit
First backtrace of the running GDB

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-18257-listarch-gdb-prs=sources.redhat.com@sourceware.org Wed Jun 24 11:17:17 2015
Return-Path: <gdb-prs-return-18257-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 57196 invoked by alias); 24 Jun 2015 11:17:16 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 57163 invoked by uid 48); 24 Jun 2015 11:17:16 -0000
From: "szotsaki at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/18590] New: GDB memory leak (5+ GB) with Qt Creator in
 python theDumper.showData
Date: Wed, 24 Jun 2015 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.8
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: szotsaki at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-18590-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-q2/txt/msg00451.txt.bz2
Content-length: 888

https://sourceware.org/bugzilla/show_bug.cgi?id\x18590

            Bug ID: 18590
           Summary: GDB memory leak (5+ GB) with Qt Creator in python
                    theDumper.showData
           Product: gdb
           Version: 7.8
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: szotsaki at gmail dot com
  Target Milestone: ---

In my project the program stopped at a break point and then Qt Creator wanted
to show the stack with pretty printing. However, in a minute GDB used around 5
GB of memory and was growing further.

I attach the following files:
- gdb bt-1 and gdb bt-2: two backtraces of GDB at different times
- gdb issued commands: the issued commands by Qt Creator

--
You are receiving this mail because:
You are on the CC list for the bug.


       reply	other threads:[~2015-06-24 11:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18590-4717@http.sourceware.org/bugzilla/>
2015-06-24 11:17 ` szotsaki at gmail dot com [this message]
2015-06-24 11:18 ` szotsaki at gmail dot com
2015-06-24 15:24 ` szotsaki at gmail dot com
2015-10-10 17:51 ` szotsaki at gmail dot com
2023-06-09 20:04 ` tromey at sourceware dot org

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=bug-18590-4717-ZDjyPnr48u@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).