public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29188] gdb too slow and hogs memory for debug binary generated with gcc 11.2
Date: Fri, 27 May 2022 13:43:30 +0000	[thread overview]
Message-ID: <bug-29188-4717-EyJ1dJit2W@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29188-4717@http.sourceware.org/bugzilla/>

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

--- Comment #7 from Simon Marchi <simark at simark dot ca> ---
(In reply to Tom Tromey from comment #6)
> I tend to think this is a dup as well.
> 
> The way gcc emits the macro info also triggered a problem with mold.
> Maybe gdb should just ignore imports of 0x0 as a workaround.

I'm just worried that there could be legitimate cases of "import 0".

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

  parent reply	other threads:[~2022-05-27 13:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 17:30 [Bug gdb/29188] New: " rajpal.gusain at gmail dot com
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 [this message]
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-EyJ1dJit2W@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).