This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] -stack-select-frame


Nick Roberts wrote:

[Jason - Sorry if you get this twice.  My first message bounced at RedHat, for
some reason.]

> > I thought it would save some time if the user doesn't need to see the
> > whole stack.
> > FWIW we've done a lot of careful timing analysis, and the back & > forth communication between our GUI and gdb is so fast as to be > pointless to optimize. We original considered adding special purpose > "give Xcode everything it needs to know at a breakpoint hit" type > commands but when we saw how fast the majority of MI commands can > execute & be parsed by the GUI, it was obvious that this was not a > useful area to optimize. And frankly, in my anecdotal experience, > MacOS X isn't the fastest OS at things like "two processes talking > over a pipe".


You've clearly been more quantitative.  With my limited resources, I'm
just guessing what might work best.  I've suggested to Daniel a change
that, I hope, won't impact on Xcode.  I think you have your own copy
of GDB and, like you say, you don't really care, but I guess its best
not to diverge more than necessary.

Ideally, future versions of Apple GDB will be much more like FSF GDB.
I'm hip-deep in a merge right now, and adding lots of local markers
so we can pick out candidate patches more easily; once all that's
done, we should be able to start contributing more (starting with
the basic Darwin native bits, it's a nuisance to have to use other
configs to test even trivial patches).

Stan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]