Re: Refuses to break [solved]
Re: Refuses to break [solved]
- Subject: Re: Refuses to break [solved]
- From: Norio Ota <email@hidden>
- Date: Fri, 3 Dec 2004 11:11:54 +0900
I see. I don't use Objective C, I didn't know the meaning of 'category'.
I thought it was just a sort of Group in Groups & Files.
I'm sorry, but it might have little to do with my case.
Norio
On 2004/12/02, at 23:50, Jonathan E. Jackel wrote:
I had divided my class into categories so that the files would be more
manageable. They are just regular Objective C categories. XCode does
not
seem to allow debugging in categories sometimes. Moving the methods
from
the category files to the main class files restored the ability to
debug.
JJ.
-----Original Message-----
From: Norio Ota [mailto:email@hidden]
Sent: Wednesday, December 01, 2004 7:00 PM
To: Jonathan Jackel
Cc: email@hidden
Subject: Re: Refuses to break [solved]
Jonathan,
Since getting rid of the .mode1 file did not work either, I'd like to
try that. Could you tell me what 'my categories' are more detail?
Norio
On 2004/12/01, at 22:39, Jonathan Jackel wrote:
Getting rid of the .mode1 file did not work. I reconsolidated my
categories into the main class file and now it works fine. Not the
most convenient compromise, but at least I can debug.
Jonathan
On Nov 29, 2004, at 7:37 PM, Frank Rimlinger wrote:
When the debugger or indeed any part of Xcode just obviously doesn't
work, the first thing to do is to throw out a file that caches some
user preferences in the Xcode project. I find that nine times out
of
ten this solves the problem. To do this, first be sure Xcode is not
running. Now right click on your xxx.xcode project icon in a finder
view (the blue icon with an "A" on it). Select "Show package
contents". This will open up an new folder. Locate the file
<user>.mode1, where <user> is your user name. Drag this file to the
trash and empty the trash. Be sure *not* to drag any of the other
files to the trash. If the situation does not improve, re-install
Xcode from the CD or CD image. Now create a fresh version of any of
the standard projects, and try running it in the debugger. If that
works, migrate your old project to the good one and hope for the
best. If that doesn't work, try re-installing OS X. If you use
Java, re-install with the latest version from the Apple web-site.
As
a last resort, back up and re-initialize your hard disk. If the
problem still persists, its time to start thinking about hardware
diagnostics.
The moral is, Xcode 1.5 does work well most of the time, but it can
go sour for no apparent reason. I find it much easier to just deal
with it than to figure out what is really wrong. Throwing switches
only works if you are an expert, and using the command line is a
horrible work-around, IMHO.
frank
Norio Ota wrote:
I feel much stress on debugging. I have to look at the spinning
cursor
all the time when I press some control buttons on the window by
mistake. However who can debug without pressing any control
buttons?
Even if I turn Enable Data Formatters off, Debugger does the same
behavior.
On Nov 29, 2004, at 3:08 PM, Jonathan Jackel wrote:
My project now refuses to honor breakpoints in my document class
(which I
have broken up into categories). Symbolic breakpoints work
sometimes, but
not always. Normal breakpoints don't work at all in the affected
files, but
everything seems normal with other files.
_______________________________________________
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