public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "noelgrandin at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/26491] New: second run of program very slow Date: Thu, 20 Aug 2020 12:39:45 +0000 [thread overview] Message-ID: <bug-26491-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26491 Bug ID: 26491 Summary: second run of program very slow Product: gdb Version: 9.1 Status: UNCONFIRMED Severity: minor Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: noelgrandin at gmail dot com Target Milestone: --- Created attachment 12784 --> https://sourceware.org/bugzilla/attachment.cgi?id=12784&action=edit perf flame graph version 9.1-5 running on Fedora 32 I am running LibreOffice unit tests. (e.g. make CppunitTest_chart2_import) The first time I debug something, I get this (gdb) r ... starts within 10 seconds.... .. I stop stuff... ... process exits... (gdb) r ... now it takes 5 mins to get going again .... This is on a pretty decent box (4Ghz i7) I attach a flame graph. I am building with clang, and with --enable-split-debug --enable-gdb-index if that makes any difference. Funnily, this only seems to apply to the unit tests, the actually main binary (soffice) is fine. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-08-20 12:39 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-20 12:39 noelgrandin at gmail dot com [this message] 2020-08-24 10:17 ` [Bug c++/26491] " noelgrandin at gmail dot com 2020-08-24 12:03 ` simark at simark dot ca 2020-08-24 16:18 ` noelgrandin at gmail dot com 2020-08-24 16:20 ` noelgrandin at gmail dot com
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-26491-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).