public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vanboxem.ruben at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug win32/14619] New: Slow startup when built without --disable-nls Date: Tue, 25 Sep 2012 09:53:00 -0000 [thread overview] Message-ID: <bug-14619-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14619 Bug #: 14619 Summary: Slow startup when built without --disable-nls Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: win32 AssignedTo: unassigned@sourceware.org ReportedBy: vanboxem.ruben@gmail.com Classification: Unclassified On Windows, when starting a Qt GUI "Hello World!" style app, startup time on my 8GB RAM Core i5 2.5-3.2 GHz is dramatically increased when gdb is not built without nls. Doing gdb testapp set verbose on run shows me that the delay is due to symbol loading of QtCore4d (2 vs 6 seconds) and QtGui4d (6 vs 18 seconds). The times are counted by me and recorder visually. The issue is discussed here: http://sourceforge.net/mailarchive/message.php?msg_id=29795741 Where the "rubenvb" build left out --disable-nls and the mingw-builds didn't. I built gdb with --disable-nls seperately and verified it improves the times as described above and in that thread. I'm sure this isn't wanted. Providing a minimal testcase will be difficult, the Qt debug DLL's involved are quite large, but it should be reproducible with the official Qt installer and for example my GCC 4.7.1 32-bit toolchains' gdb. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-09-25 9:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-25 9:53 vanboxem.ruben at gmail dot com [this message] 2012-09-25 9:53 ` [Bug win32/14619] " vanboxem.ruben at gmail dot com 2012-09-26 0:53 ` asmwarrior at gmail dot com 2012-09-27 8:35 ` vanboxem.ruben at gmail dot com 2012-09-27 15:28 ` tromey at redhat dot com 2012-09-28 10:48 ` vanboxem.ruben at gmail dot com 2012-09-28 15:27 ` tromey at redhat dot com 2023-02-11 17:50 ` 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-14619-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).