From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit/dwarf] Create partial symbols for nested subprograms
Date: Thu, 11 Sep 2008 22:44:00 -0000 [thread overview]
Message-ID: <m3bpyu2tjh.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080911183730.GA17809@caradoc.them.org> (Daniel Jacobowitz's message of "Thu\, 11 Sep 2008 14\:37\:30 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Joel> . To measure the startup time, I used the --statistics command-line
Joel> switch.
Daniel> I usually use 'gdb -batch foo.exe' to time reading partial
Daniel> symbols
FWIW -- me too.
Joel> It looks like roughly a 4% increase in startup time. Not sure whether
Joel> that's considered a large increase or not - I just think that it's not
Joel> noticeable. None of our users have reported issues with startup time.
How much memory do you have on your machine? Are you using a 32- or
64-bit machine? And how many objfiles are made with this test
program?
I am just curious to know what differs between my tests and yours. In
my case, I start the system OpenOffice writer and then attach to it.
I have all the debuginfo packages installed. I'm using x86, and on
this machine with that test, gdb takes 256569344 bytes (measured by
maint space 1) and it takes about 1:00 elapsed time to start up. I
think there are 262 objfiles created, half of them for separate
debuginfo (this is from memory, I could be off by a little).
Daniel> Your users must be more patient than mine or Tom's :-) I consider
Daniel> startup time to be pretty important, and I've been working on bringing
Daniel> it down... Tom's been working on an even more drastic version.
FWIW I don't think Joel's patch will negatively affect my current
approach.
Tom
next prev parent reply other threads:[~2008-09-11 22:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 20:20 Joel Brobecker
2008-09-10 20:35 ` Daniel Jacobowitz
2008-09-10 21:38 ` Tom Tromey
2008-09-11 5:01 ` Joel Brobecker
2008-09-11 22:15 ` Tom Tromey
2008-09-11 22:28 ` Daniel Jacobowitz
2008-09-11 22:33 ` Tom Tromey
2008-09-12 4:19 ` Joel Brobecker
2008-09-11 17:55 ` Joel Brobecker
2008-09-11 18:38 ` Daniel Jacobowitz
2008-09-11 21:53 ` Joel Brobecker
2008-09-13 15:14 ` Daniel Jacobowitz
2008-09-13 22:21 ` Joel Brobecker
2008-09-11 22:44 ` Tom Tromey [this message]
2008-09-12 4:18 ` Joel Brobecker
2008-09-12 16:51 ` Tom Tromey
2008-09-12 16:56 ` Joel Brobecker
2008-09-12 17:19 ` Tom Tromey
2008-09-12 17:43 ` Joel Brobecker
2008-09-12 18:08 ` Tom Tromey
2008-09-12 18:43 ` Frank Ch. Eigler
2008-09-12 20:31 ` Tom Tromey
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=m3bpyu2tjh.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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