Ah! Bullseye!
On 18/07/2011, at 14:13 , Quincey Morris wrote:
> Is this in Xcode 4? Make sure the "level of detail" slider at the bottom of
> the debugger view in the navigator pane is all the way to the right. If it's
> in its default middle position, it often collapses the call stack, mislea
As was pointed out below the CString doesn't support instance method string:.
Crashing this in a debugger should give you call stack so you can trace who is
doing the calling. You should also have a crash log that can be symbolized.
But, if this is your code run it in the debugger and have it c
On Jul 18, 2011, at 05:48, Andre Masse wrote:
> -[NSCFString string]: unrecognized selector sent to instance 0x7fff71192b70
I don't think anyone's pointed you in the direction of *reading* this error
message. Note that it says -[NSCFString string], not +[NSCFString string].
Someone has sent a '
On Mon, Jul 18, 2011 at 7:20 AM, Vincent Habchi wrote:
> Try to use the Zombies Instrument. If you're sending a message to a
> deallocated object (as this is certainly the case), it will pop up.
Yes, this is the best idea. You can then follow the history of that
address and see what used to live
On Jul 17, 2011, at 7:34 PM, Andre Masse wrote:
> -[NSCFString string]: unrecognized selector sent to instance 0x7fff71192b70
>
> Is there a way to know which instance is referred at that address? I tried
> "info symbol *0x7fff71192b70" in gdb and all i get is a blank line. The
> address is con
err hmm - running out of ideas. That's a heck of an address by the way - you
must be in 64 bit mode, I'm still not.
I often put a try-catch block around the body of the code in main.m NSLog()ed
the exception at that point and stuck in a breakpoint. I do that because I have
had issues with unha
Andre,
> Any other ideas?
Try to use the Zombies Instrument. If you're sending a message to a deallocated
object (as this is certainly the case), it will pop up.
Bonne chance ! ;)
Vincent
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Plea
Hi,
Still banging my head on this one. Here's what I've done:
1- Adding a breakpoint on objc_exception_throw: brings the debugger on
NSApplicationMain...
2- I've enabled MallocStackLoggingNoCompact environment variable. After my app
crashes, I've tried
shell malloc_history 1480 0x7fff71192b
Salut ! :)
> I'm having problems tracking down this bug:
>
> -[NSCFString string]: unrecognized selector sent to instance 0x7fff71192b70
Besides anything that was already mention, I may add that this kind of error is
frequently caused by the object being freed and its memory reused by another
Reference to documentation:
http://developer.apple.com/library/mac/#recipes/xcode_help-breakpoint_navigator/articles/adding_an_exception_breakpoint.html%23//apple_ref/doc/uid/TP40010433-CH1-SW1
Kiel
On 18/07/2011, at 10:34 AM, Andre Masse wrote:
> Hi,
>
> I'm having problems tracking down this
Hi Andre,
To help you debug this problem, I suggest you set a breakpoint on the
objc_exception_throw exception symbol. Using Xcode 4, this can be done by:
1) From the main menu bar choose View > Navigators > Breakpoint.
2) At the very bottom left of the project window, click the "+" button.
3) F
Google up mallocstackloggingnocompact. Bill Bumgarner had a good article on it.
That would help you track memory actually allocated.
On Jul 18, 2011, at 8:34, Andre Masse wrote:
> Hi,
>
> I'm having problems tracking down this bug:
>
> -[NSCFString string]: unrecognized selector sent to in
Hi,
I'm having problems tracking down this bug:
-[NSCFString string]: unrecognized selector sent to instance 0x7fff71192b70
Is there a way to know which instance is referred at that address? I tried
"info symbol *0x7fff71192b70" in gdb and all i get is a blank line. The address
is consistent a
13 matches
Mail list logo
