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/29702] Huge slowdown just after loading thread DWARF data when hitting breakpoints (gdb in MCUXpresso / Eclipse) Date: Fri, 21 Oct 2022 17:12:06 +0000 [thread overview] Message-ID: <bug-29702-4717-WEW6mMiTfL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29702-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29702 Simon Marchi <simark at simark dot ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simark at simark dot ca --- Comment #2 from Simon Marchi <simark at simark dot ca> --- To make the problem easier to investigate, you can try to manually trigger the expansion of symtabs using the "maintenance expand-symtabs" command. You don't need to be connected to your target to do this. For instance (running gdb on gdb): (top-gdb) with debug timestamp 1 -- with debug dwarf-read 1 -- maintenance expand-symtabs finish 1110674.433796 [dwarf-read] process_queue: Expanding one or more symtabs of objfile /home/simark/build/binutils-gdb/gdb/gdb ... 1110674.433821 [dwarf-read] process_queue: Expanding symtab of CU at offset 0x47aa3b3 1110674.489215 [dwarf-read] process_queue: Done expanding CU at offset 0x47aa3b3 1110674.489236 [dwarf-read] process_queue: Done expanding symtabs of /home/simark/build/binutils-gdb/gdb/gdb. If you can reproduce the delay this way, it will be much easier to investigate. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-21 17:12 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 [this message] 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 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-WEW6mMiTfL@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).