public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "rajpal.gusain at gmail dot com" <sourceware-bugzilla@sourceware.org> 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 [thread overview] Message-ID: <bug-29188-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29188 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=14115&action=edit 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 memory consumption of gdb process also goes up significantly. 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 doing backtrace and breakpoint completion and that's the only information I can share right now. Debugging in general is painstakingly slow and almost impractical. I did try to compile with dwarf4 format but it doesn't seem to help with the gdb performance. 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. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-05-26 17:30 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-26 17:30 rajpal.gusain at gmail dot com [this message] 2022-05-26 18:06 ` [Bug gdb/29188] " simark at simark dot ca 2022-05-26 18:24 ` rajpal.gusain at gmail dot com 2022-05-26 18:41 ` simark at simark dot ca 2022-05-27 10:52 ` rajpal.gusain at gmail dot com 2022-05-27 12:50 ` simark at simark dot ca 2022-05-27 12:57 ` tromey at sourceware dot org 2022-05-27 13:43 ` simark at simark dot ca 2022-05-27 15:11 ` rajpal.gusain at gmail dot com 2022-06-03 20:31 ` rajpal.gusain at gmail dot com 2022-06-04 16:12 ` tromey at sourceware dot org 2022-06-04 17:46 ` rajpal.gusain at gmail dot com 2022-10-25 16:16 ` 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-29188-4717@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).