From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E67A4383820C; Thu, 26 May 2022 17:30:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E67A4383820C From: "rajpal.gusain at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/29188] New: gdb too slow and hogs memory for debug binary generated with gcc 11.2 Date: Thu, 26 May 2022 17:30:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 11.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: rajpal.gusain at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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 attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2022 17:30:18 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29188 Bug ID: 29188 Summary: gdb too slow and hogs memory for debug binary generated with gcc 11.2 Product: gdb Version: 11.2 Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: rajpal.gusain at gmail dot com Target Milestone: --- Created attachment 14115 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D14115&action=3Ded= it pstack output captured when gdb was stuck We recently migrated our projects to gcc 11.2 and it has dwarf 5 as default debugging format (unsure if it's consequential). And I notice that gdb is not liking it, debugging 11.2 compiled binary with= gdb 11.2 is pathetically slow and sometimes even backtrace takes 3 mins and mem= ory consumption of gdb process also goes up significantly.=20 I then tried old gdb 8.3 and I still have same problem I dumped pstack on gdb process (with gdb 8.3) when it was churning wheels d= oing backtrace and breakpoint completion and that's the only information I can s= hare right now. Debugging in general is painstakingly slow and almost impractical.=20 I did try to compile with dwarf4 format but it doesn't seem to help with the gdb performance.=20 Are there any suggestions/workarounds to deal with this issue? Let me know if any other information is needed. Binary was compiled with -g3 option. --=20 You are receiving this mail because: You are on the CC list for the bug.=