Re: Xcode debugging UI question
Re: Xcode debugging UI question
- Subject: Re: Xcode debugging UI question
- From: Scott Tooker <email@hidden>
- Date: Wed, 3 Aug 2005 14:00:22 -0700
On Aug 3, 2005, at 1:19 PM, Bill Monk wrote:
On Aug 2, 2005, at 3:17 PM, Scott Tooker wrote:
in the case of the debugger, it's perfectly happy to debug without
any debug information at all or debug optimized code.
Sure, you might want to debug optimized code. Nothing wrong with
that, just as you might want to debug without symbols. The debug
button should be be enabled in these cases.
But I'm seeing cases where the debugger can't debug. It's running,
yes, but it won't stop on any breakpoints. The Debugger window's
Threads and Variables panes display nothing.
Maybe these projects are misconfigured. Maybe there's something I
need to change. But if debugging can't do anything useful, I have
to believe the Debug button should be disabled.
Consider the Project Find panel. Doubtless the underlying search
code would run fine if asked to locate empty strings, and after
searching all my files I'm sure it would correctly report "not
found." That wouldn't be wrong, just pointless in human terms. So
the Find button is dimmed until until it can do something desirable.
Similarly, launching the debugger may be possible, but that alone
isn't a good enough reason for enabling the Debug buttons. It has
to be able to do something worthwhile Can Xcode know that? I don't
know, and the petulant-user side of me doesn't care, it just wants
things to work nicely.
If the debugger started in, like, 2 seconds, I wouldn't be
complaining about this as much. The problem isn't so much the
computer saying "look, stupid, that won't work." Rather it's having
to wait too long for the slap up side the head to arrive.
Hmm, sounds like you are debugging a binary that has no debugging
info at all. Really we need to show a warning sheet in this case
(since you might want to do it, but likely not).
Scott
What we could do is possibly post a warning ("Are you sure...")
It's OK by me. Because right now, compared with the overall speed
of the machine, debugging in Xcode is (I'm sorry to say it) rather
like using a Mac Plus. Warnings before lengthy or likely-useless
operations are needed when a minor slip equals minutes of waiting
while the computer goes out, does nothing, and comes back so you
can try it again.
_______________________________________________
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