Re: Xcode 3.2 -- Two more bugs??
Re: Xcode 3.2 -- Two more bugs??
- Subject: Re: Xcode 3.2 -- Two more bugs??
- From: Jim Ingham <email@hidden>
- Date: Mon, 31 Aug 2009 11:51:27 -0700
No it doesn't mean that. When Xcode is "running" without setting any
breakpoints, there are a lot of the pieces of information gdb normally
gathers that we know it doesn't need. So we cooked up some startup
settings that tell gdb not to notice things like shared library
loading and not to read any symbol information at all, etc. If you
only need to use gdb as a program launcher not a debugger, it doesn't
add much overhead. It's only when you want to do things like look at
symbols or set breakpoints that you start to pay for having gdb around.
Jim
On Aug 31, 2009, at 10:32 AM, Jens Alfke wrote:
On Aug 31, 2009, at 10:08 AM, Jim Ingham wrote:
But if there are other reasons why you don't want to run your app
under the debugger in the normal "Run" mode it would be interesting
to hear what they are. We tested the way Xcode runs apps under the
debugger in 3.2 with a wide variety of apps, and having the
debugger involved only added a fraction of a second, so that should
not be a big deal.
Does that mean that gdb startup performance has been greatly
improved in 10.6?! I'm used to gdb adding several seconds to an
app's launch time, in 10.5. I just checked with a medium-sided app
project of mine, on my 2.4GHz MBP, and it's five seconds from
"[Session started..." to entering main(). When I run Chromium, it's
often more like 30 seconds.
(Sadly, I can't install 10.6 yet, as it has too many problems with
VPN and LDAP on Google's intranet.)
—Jens
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden