public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "nickpelling at nickpelling dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29702] Huge slowdown just after loading thread DWARF data when hitting breakpoints (gdb in MCUXpresso / Eclipse)
Date: Tue, 25 Oct 2022 15:27:58 +0000	[thread overview]
Message-ID: <bug-29702-4717-vMDw5FaSp4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29702-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Nick Pelling <nickpelling at nickpelling dot com> ---
Hi Simon,

Yes, readelf does indeed reveal numerous suspicious-looking zero-offset macros
in our file (in fact, 16257 of them), e.g.:

 DW_MACRO_import - offset : 0x0
 DW_MACRO_start_file - lineno: 16 filenum: 3 filename:
c:\nxp\mcuxpressoide_11.1.0_3209\ide\tools\lib\gcc\arm-none-eabi\8.3.1\include/stddef.h
 DW_MACRO_import - offset : 0x0
 DW_MACRO_end_file

I'm reasonably certain that this will turn out to be the smoking gun here, so
thanks very much for your help! My next step is to try to get hold of an
updated gcc linker for the Cortex-M7 and see if that fixes the issue. I'll
update this ticket when I have more information.

Cheers, Nick

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

  parent reply	other threads:[~2022-10-25 15:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 15:15 [Bug gdb/29702] New: " nickpelling at nickpelling dot com
2022-10-21 16:53 ` [Bug gdb/29702] " tromey at sourceware dot org
2022-10-21 17:12 ` simark at simark dot ca
2022-10-24 16:50 ` nickpelling at nickpelling dot com
2022-10-24 17:07 ` simon.marchi at polymtl dot ca
2022-10-25 15:27 ` nickpelling at nickpelling dot com [this message]
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-29702-4717-vMDw5FaSp4@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).