contain: a
> conflict list with the right objects and properties that I expect to be in
> conflict. I understand the error coming back from the save, but not the call
> to objc_exception_throw.
>
> In case it matters, this is on iPhone OS 3.1.3, Xcode 3.2.2.
>
> Thanks,
>
opagate properly.
Everything works in the Distribution build without warnings, errors, etc. It's
just that objc_exception_throw gets called, and I'm wondering why. Is it a
symptom of an unrelated problem that I'm not understanding yet, is it a bug in
Core Data, or should I just
t not the call to
objc_exception_throw.
In case it matters, this is on iPhone OS 3.1.3, Xcode 3.2.2.
Thanks,
Hank
On Jun 8, 2010, at 12:08 PM, Alexander Spohr wrote:
> Is there anything in the log?
> What does save's error parameter return?
>
> atze
>
>
> Am 0
ion about this scenario - the Core Data
> Programming Guide (in Communicating Changes Between Contexts) seems to
> suggest my approach (case 3b), although there in-memory changes are preferred
> over store changes.
>
> I always have a break point set on objc_exception_t
een able to find any information about this scenario - the Core Data
Programming Guide (in Communicating Changes Between Contexts) seems to suggest
my approach (case 3b), although there in-memory changes are preferred over
store changes.
I always have a break point set on objc_exception_thr
You shoul post your code as it is difficult to discern your problem
with the way you are describing things.
In other words:
Cannot perform operation without a managed object context
What operation is being performed that could require an moc?
If I set a breakpoint:
In what, on what?
n Apr 22, 2009, at 2:20 PM, Daniel Child wrote:
(gdb) po *(int *)($ebp+8)
Cannot access memory at address 0x1
(gdb)
Something's still not right here. On Intel 32, $ebp+8 points to the
first argument in a function call, which would be the NSException
object passed into objc_exception_th
into objc_exception_throw().
Are you sure you are trying this after, and **only** after, the
debugger hits objc_exception_throw(), but before continuing execution?
If so, are you sure you are looking at the top of the stack?
If it helps, I always put the following two debugger commands in
You're right.
(gdb) po $rdi
Value can't be converted to integer.
(gdb) po *(int *)($ebp+8)
Cannot access memory at address 0x1
(gdb)
On Apr 22, 2009, at 4:16 PM, Nick Zitzmann wrote:
On Apr 22, 2009, at 2:13 PM, Daniel Child wrote:
Well, I think so. I thought all Core2 Duos run 64-bit.
Ye
On Apr 22, 2009, at 2:13 PM, Daniel Child wrote:
Well, I think so. I thought all Core2 Duos run 64-bit.
Yes, but what is the architecture of your program? Is it i386 or is it
x86_64? If it's the former, then it is not an Intel 64 program. If you
don't know, then it's probably i386.
Also
Well, I think so. I thought all Core2 Duos run 64-bit.
The build settings are for Xcode 3.1, OS 10.5. Are there any other
settings I should be concerned with?
Also, tried the Intel 32-bit, and that also said it couldn't be
converted to an integer.
On Apr 22, 2009, at 3:31 PM, Nick Zitzman
On Apr 22, 2009, at 1:28 PM, Daniel Child wrote:
It says
Running…
(gdb) po $rdi
Value can't be converted to integer.
(gdb)
Are you sure your program is running as Intel 64? The $rdi register is
only available to X86-64 applications. In 32-bit Intel apps, arguments
to functions are p
It says
Running…
(gdb) po $rdi
Value can't be converted to integer.
(gdb)
On Apr 22, 2009, at 2:56 PM, Nick Zitzmann wrote:
On Apr 22, 2009, at 12:36 PM, Daniel Child wrote:
Since none of the methods below are things I have written, I'm not
sure where to go from here. How can I go abo
On Apr 22, 2009, at 12:36 PM, Daniel Child wrote:
Since none of the methods below are things I have written, I'm not
sure where to go from here. How can I go about finding out what is
causing this?
Start by printing the exception to the console using the po command
when the exception is
hitting debug/run
causes it to hang, regardless of whether manual breakpoints are
activated. (objc_exception_throw is symbolic).
Since none of the methods below are things I have written, I'm not
sure where to go from here. How can I go about finding out what is
causing this?
T
By setting a Breakpoint at objc_exception_throw or [NSException raise]
I am able to stop my program when (for example) an out of range
exception is thrown. However the call stack trace on the debugger
window or the 'bt' command only shows a single line. For example:
#0 0x9
16 matches
Mail list logo
