Re: Breakpoints keep getting turned off
Re: Breakpoints keep getting turned off
- Subject: Re: Breakpoints keep getting turned off
- From: Han Ming Ong <email@hidden>
- Date: Tue, 8 Sep 2009 13:36:55 -0700
On Sep 8, 2009, at 12:26 AM, Seth Willits wrote:
On Sep 8, 2009, at 12:15 AM, Joar Wingfors wrote:
It was driving me bonkers so I finally figured this out. Using Cmd-
R is now running with breakpoints off. I've been using Cmd-R since
the beginning of time and I swear it hasn't done this to me until
now. I don't know when or why this changed, but it's going to be a
heck of an effort to change to using Cmd-Y all the time.
You can always remap the keyboard shortcuts: Xcode Preferences >
Key Bindings.
Good idea. Though if I do want to run without the breakpoints, Cmd-R
will then always enable them and I'll have to remember to use Y ;-)
The thing I don't understand about this is that Cmd-R always runs
with them disabled, and Cmd-Y always runs with them enabled. That in
itself is fine and understandable, by what is the point of the
Breakpoints toolbar button that enables/disables breakpoints? While
the app is running, I can click on that button to enable/disable
them, but if I use Cmd-R or Y, the state of the button is ignored.
It seems the toolbar button's state is only useful for if you
actually *click* on the Build & Run/Debug button, or if the app is
already running. The first part of that is confusing given the prior
behavior. :-\
"Oh well", I suppose.
Seth,
(option)-command-R is supposed to be associated with 'Running' (i.e.,
with Breakpoints Off)
(option)-command-Y is supposed to be associated with
'Debugging' (i.e., with Breakpoints On).
A lot of us are still wired to those short cuts, so we made sure that
in 3.2, we preserve the semantics. If you find that command-R actually
turning Breakpoints On (If you show icons on your toolbar, it should
be quite clear whether the Breakpoints button is in a pressed state or
not), you should file a bug.
Now, just to be clear, even during 'Running', we are using gdb as the
launcher, so you will see some logs in the Console (the motivation for
using gdb as the launcher is to allow gdb to catch crash with vastly
accurate stack trace than using Xcode as the launcher). So you might
be mistaken that you are 'Debugging' when you hit command-R.
The best indication of whether you are Running or Debugging is looking
at the Breakpoints button or the badge on the Run/Debug button.
Finally, we do have a newer short-cut to launch an application: option-
command-return. So you always only need to remember one short cut to
launch an app. This is key off the state of the Breakpoints button. If
you want to launch Running, make sure the Breakpoints button is off.
Otherwise, make sure that the Breakpoints button is on. Our
observation has been that people who started using Xcode since 3.x
seem to have no problems grasping this new concept.
Using myself as an anecdotal evidence, I used to be so hard-wired to
option-command-R and option-command-Y that I thought it would be
impossible for me to change. But recently, with gdb's launch time
greatly improved, I find myself always having Breakpoints On and
hitting option-command-return.
Also, like Joar mentioned, the Breakpoints button allows people who
are running to quickly go into Debug mode. The other way is also true.
Without the Breakpoints button, the steps to achieve both actions are
a bit cumbersome.
Hope that helps, Han Ming
_______________________________________________
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