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] Slow startup when built without --disable-nls
Date: Thu, 27 Sep 2012 08:35:00 -0000 [thread overview]
Message-ID: <bug-14619-4717-334BNnSTif@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14619-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14619
--- Comment #2 from vanboxem.ruben at gmail dot com 2012-09-27 08:34:54 UTC ---
(In reply to comment #1)
> Does this a 64bit gdb issue or 32bit gdb issue?
> I read the post:
> http://sourceforge.net/mailarchive/message.php?msg_id=29795741
> They said they were using "mingw64-gcc-4.7.1-2-rubenvb and Mingw-builds-4.7.1
> (both 64 bit native) in Qt Creator".
It is not specific to 64-bit. I just built and tested a 32-bit Qt with my 4.7.2
32-bit toolchain and slow gdb, and startup is about 16 seconds. Switching to a
gdb configured with --disable-nls makes that startup time about 6 seconds.
--
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 prev parent reply other threads:[~2012-09-27 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 9:53 [Bug win32/14619] New: " vanboxem.ruben at gmail dot com
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 [this message]
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-334BNnSTif@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).