public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "rdiezmail-binutils at yahoo dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/23710] gdb is slow and memory hungry consuming debug generated with LTO by GCC Date: Wed, 07 Apr 2021 07:25:25 +0000 [thread overview] Message-ID: <bug-23710-4717-2ZD7uSCmXa@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-23710-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=23710 --- Comment #18 from rdiezmail-binutils at yahoo dot de --- Could someone clarify the status of this issue? Is a fix going to land soon? I would also like to know what the last version of GDB is without this issue, if any. And whether it would still work with newer GCC versions. Yesterday, GDB used too much memory on my PC. It even managed to freeze my Linux system, to the point that not even the mouse cursor was moving. I had to pull the power cord. I don't have a swap file, but the OOM killer did not trigger. I am using a toolchain similar to this one: https://github.com/rdiez/JtagDue/blob/master/Toolchain/Makefile But I am targetting an embedded ARM Cortex-M4 at the moment. The toolchain component versions I was using were: BINUTILS_VERSION := 2.35.1 GMP_VERSION := 6.2.1 MPFR_VERSION := 4.1.0 MPC_VERSION := 1.2.1 GCC_VERSION := 10.2.0 NEWLIB_VERSION := 4.0.0 GDB_VERSION := 10.1 GDB version 10.1 was sluggish with LTO release builds, but because I normally use non-LTO debug builds, I have put up with this issue for a long time. However, I recently upgraded these toolchain component versions and rebuilt the toolchain: BINUTILS_VERSION := 2.36.1 NEWLIB_VERSION := 4.1.0 After the upgrade, GDB started using gigabytes of memory when programming the firmware. The embedded firmware I am building has changed too, but it is very similar, so it is hard to say if any particular change, for example #including more files (which could bring in more debug symbols), has triggered the problem. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-07 7:25 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23710-4717@http.sourceware.org/bugzilla/> 2020-03-08 11:09 ` vries at gcc dot gnu.org 2020-03-08 13:14 ` jan.kratochvil at redhat dot com 2020-03-17 7:56 ` cvs-commit at gcc dot gnu.org 2020-03-20 9:06 ` vries at gcc dot gnu.org 2020-04-02 12:39 ` vries at gcc dot gnu.org 2020-07-15 9:43 ` rdiezmail-binutils at yahoo dot de 2020-07-16 12:51 ` rdiezmail-binutils at yahoo dot de 2020-11-24 11:03 ` rdiezmail-binutils at yahoo dot de 2021-03-09 19:08 ` hi-angel at yandex dot ru 2021-04-07 7:25 ` rdiezmail-binutils at yahoo dot de [this message] 2021-05-31 12:14 ` vries at gcc dot gnu.org 2021-06-10 18:35 ` tromey at sourceware dot org 2021-06-10 22:59 ` vries at gcc dot gnu.org 2021-06-11 15:02 ` tromey at sourceware dot org 2021-06-22 13:24 ` vries at gcc dot gnu.org 2022-06-17 19:06 ` jsm28 at gcc dot gnu.org 2022-06-17 19:12 ` dpmendenhall at gmail dot com 2022-06-18 18:13 ` tromey at sourceware dot org 2022-06-20 6:59 ` rguenth at gcc dot gnu.org 2023-01-18 13:47 ` fabian@ritter-vogt.de 2023-01-19 2:25 ` sam at gentoo 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-23710-4717-2ZD7uSCmXa@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: linkBe 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).