public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug macros/27754] Excessive CPU load and memory usage with -g3 debug info Date: Fri, 18 Nov 2022 02:24:05 +0000 [thread overview] Message-ID: <bug-27754-4717-u9iqxhJSOe@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27754-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27754 --- Comment #28 from Tom Tromey <tromey at sourceware dot org> --- (In reply to Pedro Alves from comment #27) > Did you mean that you no longer think that "this could in theory yield the > wrong answer sometimes, though." ? I don't really remember what I meant, but it seems to me that, while ignoring imports of 0x0 is maybe technically wrong, on the other hand it's a workaround for what appears to be a reasonably common problem. > This issue just came up again in a discussion Simon and I were having, and I > was also wondering whether we could make GDB skip reimporting the same > offset. Maybe just ignoring 0x0 is enough and we don't need to worry about the other cases? Anyway it seems fine to me to do this. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-11-18 2:24 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-19 16:03 [Bug gdb/27754] New: " rdiezmail-binutils at yahoo dot de 2021-04-19 16:04 ` [Bug gdb/27754] " rdiezmail-binutils at yahoo dot de 2021-04-19 17:02 ` dblaikie at gmail dot com 2021-04-19 17:07 ` psmith at gnu dot org 2021-04-23 18:38 ` tromey at sourceware dot org 2021-04-23 18:56 ` tromey at sourceware dot org 2021-04-23 20:31 ` rdiezmail-binutils at yahoo dot de 2021-04-23 20:52 ` dblaikie at gmail dot com 2021-05-06 11:13 ` rguenth at gcc dot gnu.org 2021-05-06 11:45 ` rdiezmail-binutils at yahoo dot de 2021-05-06 12:34 ` rdiezmail-binutils at yahoo dot de 2021-05-10 14:27 ` [Bug macros/27754] " tromey at sourceware dot org 2021-05-10 14:51 ` tromey at sourceware dot org 2021-05-10 20:30 ` tromey at sourceware dot org 2021-05-11 8:15 ` rguenth at gcc dot gnu.org 2021-05-11 8:19 ` jakub at redhat dot com 2021-05-12 20:37 ` simark at simark dot ca 2021-05-12 20:38 ` simark at simark dot ca 2021-05-13 17:20 ` tromey at sourceware dot org 2021-05-13 17:26 ` jakub at redhat dot com 2021-05-13 17:31 ` simark at simark dot ca 2021-12-21 21:25 ` rdiezmail-binutils at yahoo dot de 2021-12-21 21:26 ` rdiezmail-binutils at yahoo dot de 2021-12-22 20:27 ` ssbssa at sourceware dot org 2021-12-23 2:48 ` simark at simark dot ca 2021-12-23 16:36 ` ssbssa at sourceware dot org 2022-10-25 16:16 ` tromey at sourceware dot org 2022-10-25 16:16 ` tromey at sourceware dot org 2022-10-25 16:19 ` tromey at sourceware dot org 2022-10-25 16:43 ` rdiezmail-binutils at yahoo dot de 2022-10-25 16:58 ` rajpal.gusain at gmail dot com 2022-11-17 20:04 ` pedro at palves dot net 2022-11-18 2:24 ` tromey at sourceware dot org [this message]
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-27754-4717-u9iqxhJSOe@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).