1. Code
  2. iOS SDK

Quick Tip: Customize NSLog for Easier Debugging

Read Time:4 minsLanguages:

In this quick tip we are going to learn how to customize the output generated by NSLog in order to debug programs more efficiently. Read on!


By default, NSLog displays output in the following format:

A real-world example might look like this:

The default output is good, but it leaves something to be desired. Most of the time, we want to see the following in a log statement:

  • Name of the source file where NSLog() was called
  • Source code line number where NSLog() was called
  • Name of the class and method where NSLog() was called
  • Hide date time stamp, application name, and process id info
  • Enable/disable log information by changing mode (e.g. debug, release, staging)

In short, we would like NSLog to be more like this:


Let's first look at how NSLog works unaltered. NSLog is just a C function built into the foundation framework of Cocoa, and behaves just like any other variadic C function. Specifically, NSLog sends error messages to the Apple System Log facility. It does this simply by passing its arguments along to the NSLogv function.

Because NSLog is just a wrapper for NSLogv, we can redefine NSLog with our own custom call to NSLogv. That is exactly what I will show you how to do in this tutorial.

1. Start a New Project

Create a new iOS project in Xcode, with the Empty Application template. Call it ExtendNSLog. Check the option for Automatic Reference Counting, but uncheck the options for Core Data and Unit Tests.

Create An iOS project with the Empty Application template
Product name should be "ExtendNSLog"

2. Create an Objective-C Class

Now create a header file along with the project. Select New File > Objective-­C Class. Set the name of the class to ExtendNSLogFunctionality. which will be a subclass of NSObject.

Create an Objective-­C class template
Set the class name to ExtendNSLogFunctionality

3. Add Custom NSLog Logic

Step 1

Open ExtendNSLogFunctionality.h and place the following code within the header:

The above conditional will define an NSLog statement only when DEBUG is defined. When DEBUG is not defined, the NSLog statement will do nothing. The question arises: how do you control when DEBUG is defined? This can be done by assigning DEBUG=1 in the preprocessor settings for your project.

To do so, click on your application target, and select the Build Settings tab. Next make sure that the "All" and "Combined" options are selected. Search for "preprocessing" and locate the section titled "Preprocessor Macros". Next, simply add "DEBUG=1" to the Debug section.

Add the DEBUG=1 flag to the preprocessor settings

Note that in more recent Xcode project templates, there will already be a DEBUG=1 macro defined for the Debug build configuration in the Preprocessor Macros section. For more information, refer to this post on StackOverflow.

Step 2

With the debug macro defined, our next task is to write the custom version of NSLog. Open ExtendNSLogFunctionality.m and add the following code:

Step 3

Now add the ExtendNSLogFunctionality.h include to the prefix header file Prefix.pch within the #ifdef __OBJC__ section.

For a better understanding on prefix headers, have a look at this entry on Wikipedia. Regarding prefix header best practices, check out this StackOverflow post.

4. A Custom Log Example

Now add an NSLog anywhere in your project code. In my case, I decide to add one within AppDelegate.m’s ­method -(BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions.

If you build and run the project with the Debug configuration now, you should see something like this:

Cheers! This output is much more useful than the default implementation. Hopefully you find that this technique will save you a lot of time while debugging your own programs!

Looking for something to help kick start your next project?
Envato Market has a range of items for sale to help get you started.