CODEWITHSUNDEEP
objective-cxcode4.2
DarkLeafyGreen
DarkLeafyGreen

Reputation: 70466

Why is my xcode 4.2 log always empty?

in a method that is accessed three times I want to write something to the log.

NSLog(@"%@", [response responseString]);

But there is nothing in the log. The log windows is completely white. Normally when I start an application there is always some stuff that shows up in the log but now it is totally empty.

How can I fix this?

Upvotes: 0

Views: 284

Answers (4)

Richard Collins
Richard Collins

Reputation: 85

Today I have been frustrated with a similar problem. When the console is activated, only the variables pane is showing. No sign of the console pane. After finding Debug Area Help via right clicking in the variable pane, i could see that it is meant to sit next to it on the right.

The key for me was to Hide the Utilities panel. For me, the little buttons shown in Luke's answer above would not appear until hiding and unhiding the Utilites panel.

Upvotes: 0

Luke
Luke

Reputation: 11476

Perhaps a really silly thing, but in the top right-corner of the console you should see this:

Check that the middle segment or right segment is selected.

Upvotes: 3

Michael Dautermann
Michael Dautermann

Reputation: 89549

When Console isn't behaving nicely for me (which happens sometimes when I'm doing driver level stuff or multi-threaded apps), a much more reliable thing to do is something like:

- (void) printToLog: (NSString *) aFormattedStringToPrint
{
    // don't forget to remove an older copy of this file before 
    // your app finishes launching
    FILE * aFile = fopen( "/tmp/debuggingoutput.txt", "a");
    if(aFile)
    {
         fprintf(aFile, "%s", [aFormattedStringToPrint UTF8String];
         fflush(aFile);
         fclose(aFile);
    }
}

(you can define a macro like LOGTHIS which might toggle between NSLog and the above more direct and to the point code)

And then you can "tail -f /tmp/debuggingoutput.txt" in your Terminal window while debugging and if nothing appears there, then you know your debugging lines aren't getting hit.

Upvotes: 0

dbgrman
dbgrman

Reputation: 5681

NSString *responseString = [response responseString];
NSLog(@"%@", responseString);

set a breakpoint on the first line and debug the application to see if its coming in this code in the first place. If it is, hover over responseString and it will tell you whether it is nil or not.

Upvotes: 0

Related Questions