Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit/dwarf] Create partial symbols for nested 	subprograms
Date: Fri, 12 Sep 2008 04:18:00 -0000	[thread overview]
Message-ID: <20080912041800.GA3714@adacore.com> (raw)
In-Reply-To: <m3bpyu2tjh.fsf@fleche.redhat.com>

> 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?

Phew, all these technical questions :). I'm using a 32bit machine
(Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz) with 2GB of memory.
I'm running a 2.6.19.3 Linux kernel.

Because I cannot run the test program (all these large programs that
we got from our customers require a very precise environement to start),
I can only time "gdb EXE". As a result, I think we only end up creating
one object file for that executable.

> 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.

Yes, that's a little different, because the shared libraries have been
mapped, and so debugging info for these are loaded in as well.

> FWIW I don't think Joel's patch will negatively affect my current
> approach.

Just curious, I think I either forgot a previous discussion or missed
it entirely. What approach are you going to take?

-- 
Joel


  reply	other threads:[~2008-09-12  4:18 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
2008-09-12  4:18         ` Joel Brobecker [this message]
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=20080912041800.GA3714@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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