• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CoreDate: Can't reassign an object to a different store once it has been saved.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreDate: Can't reassign an object to a different store once it has been saved.


  • Subject: Re: CoreDate: Can't reassign an object to a different store once it has been saved.
  • From: Pierre Bernard <email@hidden>
  • Date: Fri, 21 Apr 2006 00:48:57 +0200

Ondra!

Thanks for your input.

I thought myself of breaking on -[NSException raise] only minutes after posting my message to the list.
Oddly enough such a breakpoint is never hit.


There ought to be a way to tell NSRunLoop not to swallow exception.

Pierre



On Apr 21, 2006, at 12:25 AM, Ondra Cada wrote:

Pierre,

On 21.4.2006, at 0:12, Pierre Bernard wrote:

I am seeing the following message after a 'Save as' operation on a document based CoreData application:

*** NSRunLoop ignoring exception 'Can't reassign an object to a different store once it has been saved.' that raised during posting of delayed perform with target 5862a20 and selector '_commitEditing:'

How would I go about to debug this?

Break on -[NSException raise]

I can't tell which object is affected?

Neither can I :)

I can't break on the exception as I don't know of what type its is?

All exceptions are NSExceptions(*), them "types" (if I follow you properly) are actually just strings stored inside.


The only information I have is the name of a private method.

You could break on that, too, but I guess it gets called pretty often -- in all probability, breaking on raise should be much more convenient.


(*) In Cocoa--using @throw you can indeed have any exception object (like NSString, NSObject, whatever) and it cannot be (far as I know) easily breaked on, which is one of many reasons for my belief such things like exceptions (or synchronisation) do *not* belong to language, but to libraries. Anyway, sorry for my pet rant, it is completely irrelevant here :)
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc




_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >CoreDate: Can't reassign an object to a different store once it has been saved. (From: Pierre Bernard <email@hidden>)
 >Re: CoreDate: Can't reassign an object to a different store once it has been saved. (From: Ondra Cada <email@hidden>)

  • Prev by Date: [off-topic] Re: Why do people in the UK put a u in the word color?
  • Next by Date: break on @throw (was Re: CoreDate: Can't reassign an object to a different store once it has been saved.)
  • Previous by thread: Re: CoreDate: Can't reassign an object to a different store once it has been saved.
  • Next by thread: break on @throw (was Re: CoreDate: Can't reassign an object to a different store once it has been saved.)
  • Index(es):
    • Date
    • Thread