TweetFollow Us on Twitter

Modern DebugStr
Volume Number:12
Issue Number:9
Column Tag:Debugging Aids

DebugStr, the Modern Way

Capturing your program’s iostream of consciousness

By Jon Kalb

Note: Source code files accompanying article are located on MacTech CD-ROM or source code disks.

I have a friend who spends most of his time in cutting-edge (read, “reliable tools not yet available”) environments. He likes to say: “There is no debugger; there is only DebugStr.” While he may stretch the truth, he has a point. Our friends who build source-level debugging tools are a heroic lot, but there are times when MacsBug is the only option. This article, along with the accompanying dout Library, is one attempt to make using DebugStr a little more modern.

Using DebugStr is usually a clumsy process of converting integer values to strings and concatenating Pascal strings. There had to be a better way, I thought. That’s when it occurred to me to implement the low-level debugger as a C++ output stream.

The Solution Domain

This approach may be valuable for two groups: fellow users of DebugStr, and individuals interested in using and/or implementing C++ streams. But first, some limitations:

• I use the term “library” rather loosely. The dout Library is really just a small collection of source files. I also include project files for both Metrowerks and Symantec, to demonstrate how to use the library.

• In no way does this library replace a source-level debugger. If it is possible for you to use one, do so.

• Although, for the sake of clarity, I don’t follow this practice in this article, in real code your should always surround every use of the dout stream with some type of #ifndef NDEBUG statement. (NDEBUG is the preprocessor variable that controls the assert macro found in assert.h. Define NDEBUG for shipping code, and leave it undefined for code under development.) To make this task a little easier, the dout Library includes the data statement macro, ds. For example, the line “ds(dout << myObject);” would be completely stripped if NDEBUG was defined, and would become “dout << myObject;” if NDEBUG wasn’t defined.

• Streaming the semicolon character ';' to dout is problematic. MacsBug interprets the text following a semicolon as a MacsBug command, and attempts to execute text that you intended to display.

• Below are examples of overloading the insertion operator for objects to support debugging in a streams environment. This is possible if your code base doesn’t already use insertion operator overloading for other purposes. It may be possible to use the same routine for, say, storing an object to disk and for debugging purposes, but it seems unlikely. I suggest a work-around later.

• Streaming data to dout in the constructor of a static or global object (an object that is constructed before the first line of main is executed) is problematic. More on this below.

Using the Library

To use the dout Library you must include the standard C++ iostreams and the source file debugbuf.cp. Each source file that writes to the dout stream must include the header file doutstream.

Standard Streams

You can use dout just as you would cout. For example:

#include "doutstream"
// ...
dout << "file corrupted at offset " << byteOffset << endl;
// ...
dout << "name: " << un << endl << "password: " << pw << endl;
// ...
dout << "completed pass " << i << " of " << total << endl;
// ...

You can use dout just like any standard C++ output stream, but, since the debugger is more than just a byte sink, we should be able to do more, and we can.

The dout Difference

The library defines a set of symbols that cause the stream to behave in interesting ways. Normally, the stream buffers characters until it fills a line (arbitrarily defined as 60 characters) or until the caller streams an endl. You can flush this buffer at any time by streaming an endl. (endl is the standard C++ streams manipulator function for advancing to the next line.) dout produces a blank line if there is currently no text in the stream’s buffer. To flush the buffer without creating blank lines, stream the constant doutsoftflush ('\r').

dout supports both horizontal and vertical tabs when streaming douttab ('\t') or doutverttab ('\v'). Streaming doutformfeed ('\f') flushes the buffer and inserts a line of underscores. Streaming doutbackspace ('\b') “eats” the last character in the buffer. Streaming doutsysbeep ('\a') calls SysBeep; however, just like other data, this is buffered. (To beep immediately, follow doutsysbeep with endl.)

Streaming data to dout doesn’t normally suspend your program the way that a call to DebugStr would. If you want to drop into the debugger, then stream either doutdebug ('\0') or doutdropin ('\0'). These are synonyms; either one will flush the buffer and leave you in the debugger with your application suspended. (Streaming the End-of-Text character ('\x03'), usually associated with the Enter key, will do the same thing.)

As a side-effect of using MacsBug for streaming output, we can execute MacsBug commands. If a semicolon appears in the data stream, MacsBug attempts to execute the text that follows as a MacsBug command. (This can produce unexpected results if the data you are streaming just happens to contain a semicolon.) Several commands can be executed in sequence as long as each command is preceded by a semicolon.

Although you can use the dout Library in conjunction with source-level debuggers (products from Jasik, Metrowerks and Symantec support capturing messages sent with DebugStr), only MacsBug is going to be able to interpret and execute MacsBug commands.

This is an example of using dout to execute MacsBug commands.

dout << doutcommand << "hc" << doutsoftflush;
// ...
dout << doutcommand << "dm #";
dout << (unsigned long)aPointer << endl;

Note the use of the constant doutcommand (';'), and that the stream buffer is flushed (with either endl or doutsoftflush) after each command. In this example, MacsBug executes the Heap Check command, and displays memory from the location pointed to by aPointer. The default behavior for commands is to execute the command and continue program execution. In the case of Heap Check, MacsBug suspends the execution of your program if the Heap Check finds that the heap is corrupted.

For my purposes this alone would justify using the library. The library handles conversion of integer values, there is no fooling with Pascal strings, and, the C++ implementation gives us type checking without worry. But, as they say on the infomercials: Wait, there’s more.

Extending Streams

Using C++ means that we also get extensibility.

I have included streamstructsmac.h and streamstructsmac.cp as an example of how to stream standard Macintosh types (or any structure). This is not an attempt to define insertion routines for all Macintosh Toolbox structures, only an example to show you how to declare and define insertion routines for structures that you may find useful.

Listing 1: streamstructmac.h

Declarations of Insertion Operators for Point, Rect, and BitMap

The following declarations allow Points, Rects, and BitMaps to be streamed out.

#include <iostream.h>
#include <QuickDraw.h>

// inserters

ostream &operator<<(ostream &stream, const Point &rhs);

ostream &operator<<(ostream &stream, const Rect &rhs);

ostream &operator<<(ostream &stream, const BitMap &rhs);

This is the standard way to implement insertion operator overloading to standard C++ library streams. Note that there is nothing specific to the dout Library in this set of declarations (or even in the implementation that follows). These same routines could be used to stream structures of these types to any C++ ostream.

Listing 2: streamstructmac.cp

Definitions of Insertion Operators for Point, Rect, and BitMap

The following definitions allow Points, Rects, and BitMaps to be streamed out.

#include "streamstructsmac.h"

// inserters

ostream &operator<<(ostream &stream, const Point &rhs)
 stream << ".v(" << rhs.v << ") ";
 stream << ".h(" << rhs.h << ") ";
 return stream;

ostream &operator<<(ostream &stream, const Rect &rhs)
 stream << ".t(" << << ") ";
 stream << ".l(" << rhs.left<< ") ";
 stream << ".b(" << rhs.bottom<< ") ";
 stream << ".r(" << rhs.right << ") ";
 return stream;

ostream &operator<<(ostream &stream, const BitMap &rhs)
 stream << ".baseAddr(" << (void *)rhs.baseAddr << ") ";
 stream << ".rowBytes(" << rhs.rowBytes<< ")\n";
 stream << ".bounds(" << rhs.bounds<< ") ";
 return stream;

Note that the BitMap insertion function calls the Rect insertion function without any special syntax. C++’s ability to extend the language syntax to user-defined types allows this.

The style that I use shows the field names (preceded with a '.') followed by the value of the field in parentheses. Sample output for a Point, a Rect, and a BitMap, might look like this:

.v(1) .h(2) 
.t(3) .l(4) .b(5) .r(6) 
.baseAddr(0x12345678) .rowBytes(7)
.bounds(.t(3) .l(4) .b(5) .r(6) )

This is all you need to know to use streams with structs or classes that either have no private or protected members or provide accessors for all such members. But what if you want to stream private members? This situation will arise often as you develop your own classes. The solution is to implement the insertion operator overload as always, and declare it as a friend function when declaring your class. A trivial but complete example of this is included in the source files as the class privateMembers.

Suppose that you have already defined insertion operator functions for some purpose other than debugging. For example, if you are streaming objects for persistent storage, the streamed form of your objects may not be what you would like to see streamed into the debugger. One way to work around this problem is to subclass the ostream class and make dout an object of this new subclass. Now, instead of defining the insertion operator in terms of an ostream, create an insertion operator function based on the new subclass.

The Implementation

The first thing to know about the implementation of dout is that dout is a standard C++ library ostream. Stream objects are responsible for taking inserted data, formatting it, and passing it to objects of type streambuf. It is the streambuf object that decides where the data ultimately ends up. By subclassing streambuf, we make dout possible. The library contains a debugbuf class that inherits from streambuf.

The following code, from the top of the debugbuf.cp file shows the relationships of these objects:

static debugbuf debugstream;
ostream dout(&debugstream);

dout is a standard ostream. Like all ostreams it requires a streambuf object to function; so, in the constructor, we pass the address of an object of type debugbuf, which is derived from streambuf. All of our work is done in the object of type debugbuf.

Class Declarations

The first thing to notice about the declaration of the debugbuf class is that no destructor or constructors are declared. Let’s ignore this for the moment and look at the virtual functions inherited from streambuf in the protected section.

Listing 3: debugbuf.h

Declarations of debugbuf and debugbufinit

For debugbuf, virtual member functions of streambuf are declared as well as private members required for 
implementation. For debugbufinit the declaration does not have a memory footprint.

class debugbuf: public streambuf

    //virtual ~debugbuf();

    // Construction and destruction are really handled by class debugbufinit. 
    // Initialization is done in the private routine init().


    // These protected member functions are virtual functions in the parent 
    // (streambuf) class that we override to create our behavior.

    // The name overflow may be confusing -- this just outputs a character to the 
    // stream.
    // Calls outputchar().

 virtual int overflow(int c = EOF);

    // Since this is not an input stream, we want both pbackfail() and underflow() to 
    // return EOF (thus indicating failure). It turns out that the default behavior (the 
    // base class implementation) does just that.

    //virtual int pbackfail(int c = EOF);
    //virtual int underflow();

    // we don’t do input so always return EOF
 virtual int uflow() {return EOF;}

    // we don’t do input so always return 0 chars read
 virtual int xsgetn(char *, int) {return 0;}

    // Calls outputchar() for each character.
 virtual int xsputn(const char *s, int n);

    // We use the default behavior which returns a streampos that is in an invalid 
    // position. We do not support repositioning on this stream.

    //virtual streampos seekoff(streamoff off,
    //                 ios::seekdir way,
    //                 ios::openmode which =
    //                 ios::in | ios::out);

    //virtual streampos seekpos(streampos sp,
    //                 ios::openmode which =
    //                 ios::in | ios::out);

    // We don’t support setting the buffer so we use the default which is just to 
    // return “this.”

    //virtual streambuf *setbuf(char *s, int n);

    // There is nothing to sync with, so we just do the default which is to return
    // zero, indicating no error.

    // virtual int sync();

    // Actually, as an alternative implementation it would be possible to use this 
    // function to call our soft flush routine. In practice, there would be no different 
    // result. sync() is usually only called by pubsync(), which is usually only called
    // by flush(), which is usually only called by the endl manipulator function after 
    // it has streamed ‘\n’. So the soft flush would always follow a hard flush and 
    // result in a no-op.

 kMaxDebugStrReadableString = 60,
 kSizeOfSemicolonG = 2,
 kSizeOfLengthByte = 1,
 kTabSize = 5,
 kStop = true

    // the buffer
 char pbeg[ kSizeOfLengthByte +
 kMaxDebugStrReadableString +
 kSizeOfSemic olonG];

    // location of the next streamed char
 char *pnext;

    // This always points to the end of the readable string buffer. Once it is set in 
    // init(), it is never modified
 char *pend;

    // the number of queued alerts
 int alertCount;

 void init();

 void outputchar(char c);
 void formfeed();
 void horztab();
 void backspace();
 void verttab();
 void alert();
 void addchar(char c);
 void softflush();
 void flushdebugstring(int stop = false);
 void flushalerts();

 friend class debugbufinit;

class debugbufinit
 static unsigned int count;

    // Our destructor is not virtual. It is important that objects of this class have no 
    // memory footprint. We will end up with one object of this class per translation 
    // unit (.cp file). If this class has any virtual member functions then objects of 
    // this class would have v tables in memory. Since this is not intended to be a 
    // base class for other class, there is no need to be virtual.


Of the virtual functions we inherited from streambuf, four are for input, which we don’t support. For two, pbackfail and underflow, we can just accept the default behavior, and for the other two, uflow and xsgetn, we write trivial routines that return values which indicate that reading is not supported. Two other functions, seekoff and seekpos, are for positioning the stream pointer - another feature that we can’t support. We also do not allow the caller to set our buffer, so setbuf is not supported. The sync function is also unneeded. The only routines that really do any work are overflow, which calls our private member outputchar once, and xsputn, which calls outputchar once for each character passed to it.

Our private section includes some constants defined as an enum, the buffer and the pointers that we need to manage it, a counter for buffering SysBeep calls, and our private functions. I’ll discuss the private member functions later.

We finally return to the observation that instead of constructors and a destructor for debugbuf, a separate class, the debugbufinit class, is declared. This attempts to work around a problem with static objects. Before explaining the problem and what I’ve done about it, let me point out that I have not implemented a complete solution. Do not stream to dout in the constructor of a static (or global) object unless you are prepared for your application to crash. This is called “crossing the streams”. See Ghostbusters.

dout is a static object and, like all static objects, its constructor will be called before the first line of main is executed. But the first line of main is not the first line of code that is executed. If a static object streams data to dout in its constructor, this code may be executed before dout is constructed.

There is no way to reliably order construction of static objects in different translation units (.cp files), but we do know that within translation units, static objects are constructed in the order in which they appear. That is why we have the class debugbufinit and why the header file doutstream declares a static object of this type. Note that it is not declared extern. Each translation unit that includes doutstream has its own object of type debugbufinit (which is why it is important that it does not have a memory footprint).

When the debugbufinit object is constructed, it uses its static member, count, to determine if it is the first object of its class to be constructed. If it is, then it calls the init member of the static debugstream object. The init member performs the function of a constructor for the debugbuf class. This way, debugstream gets constructed only once, at the time of the first construction of a debugbufinit object. Since init may be called before or after the real constructor is called, it is important that the constructor is a “no op”.

P.J. Plauger explains this problem, along with the solution used in his implementation of the standard library streams (cout, cin, and cerr), in his book, The Draft Standard C++ Library, which I recommend. Close inspection reveals why my implementation is not a complete solution. Although I can guarantee proper construction of the debugstream object, the same cannot be said for the dout object.

I suspect that a complete solution exists for both Metrowerks and for Symantec, but I do not believe that any single solution works for both. In any case, the complete solution is left as an exercise for the reader (I’ve always wanted to say that).

Member Function Definitions

As the listing for debugbuf.cp shows, the implementation of both debugbuf and debugbufinit is straightforward.

Listing 4: debugbuf.cp

Definitions of debugbuf and debugbufinit

The debugbuf class manages a buffer using a switch statement to differentiate between characters with 
special meanings.

#include "doutstream"

#include <string.h>// for strlen() and strcpy()
#include <OSUtils.h> // for SysBeep();

static debugbuf debugstream;
ostream dout(&debugstream);

unsigned int debugbufinit::count = 0;

// this is debug code -- performance is not a goal

void debugbuf::init() // called by friend class debugbufinit
 pbeg[0] = '\0';
 pnext = pbeg + kSizeOfLengthByte;
 pend = pnext + kMaxDebugStrReadableString;
 alertCount = 0;

int debugbuf::overflow(int c)
 if (EOF == c)
 return '\0';  // returning EOF indicates an error
 return c;

int debugbuf::xsputn(const char *s, int n)
 for (int i = 0; i < n; ++i)
 return n;// we always process all of the chars

void debugbuf::outputchar(char c)
 switch (c)
 case '\b':
 case '\f':
 case '\n':
 case '\r':
 case '\t':
 case '\v':
 case '\a':
 case '\0':
 case '\x03':

void debugbuf::backspace()
 if (pbeg[0])  // if the buffer is empty, don’t bother
    // note that alerts cannot be backspaced away -- a possible enhancement

void debugbuf::formfeed()
 strcpy(pbeg, (char *)
 pnext += strlen(pnext);

// both horizontal and verticle tabbing is done by brute
// force -- performance is not a goal
void debugbuf::horztab()
    // we don’t wrap tabs so if we are within kTabSize of
    // the end of the buffer then we just flush
 if (pend - pnext <= kTabSize)
 for (int i = 0; i < kTabSize; ++i)
 addchar(' ');

void debugbuf::verttab()
 int position = pnext - &pbeg[1];
 for (int i = 0; i < position; ++i)
 addchar(' ');

void debugbuf::alert()

void debugbuf::addchar(char c)
 *pnext++ = c;
 if (pnext == pend)

void debugbuf::softflush()
 if ('\0' != pbeg[0])

void debugbuf::flushdebugstring(int stop)
 if (!stop)
 DebugStr((unsigned char *)pbeg);
 pbeg[0] = '\0';
 pnext = &pbeg[1];

void debugbuf::flushalerts()
 while (alertCount)

 if (0 == count++)

 if (0 == --count)
    // nothing to dispose, but we should flush

The main entry points are the protected members overflow and xsputn, both of which call outputchar. outputchar uses a switch statement to call one the following if the character is “special”: flushdebugstring, softflush, formfeed, horztab, backspace, verttab, or alert. If the character is “normal” we call addchar.

• If the character being processed is doutbackspace ('\b'), we reduce the length of the Pascal string in the buffer by one and back up the pointer by one character. Of course, we check first to be certain that there is at least one character in the buffer.

• If the character being processed is doutformfeed ('\f'), we flush any characters already in the buffer, fill the buffer with underscores, then flush the underscores.

• If the character being processed is a horizontal tab or douttab ('\t'), we treat it as if it were kTabSize (5) spaces, except that we don’t wrap remaining spaces to the next line. We don’t support tab stops.

• If the character being processed is a vertical tab or doutverttab ('\v'), we calculate how many characters are currently in the buffer, flush the buffer, and add a space character for each character that had been in the buffer.

• If the character being processed is an alert ('\a'), we increment the alert counter. Since all alerts are the same (just a call to SysBeep), we can “buffer” them with just a counter.

• If the character being processed is “normal”, we process it in addchar. The new character is added to the end of the Pascal string in our buffer. When the string fills the readable string buffer, we flush the buffer by calling flushdebugstring.

Notice that I said “the readable string buffer”. The buffer is actually two bytes larger than the largest Pascal string that we can handle. This is to save room to append a semicolon and the letter “g”.

Usually when DebugStr is called, MacsBug displays the Pascal string that is passed to it and waits for commands from the user. This is not really the behavior that we want. We want the string stored in the MacsBug buffer, but we don’t want to stop the application and drop into MacsBug every time data is streamed to dout. To work around this, we take advantage of the DebugStr/MacsBug command processing feature. When MacsBug receives the string passed to it by DebugStr, it displays the contents of the string up to, but not including, the first semicolon (if there is one). Any characters after the semicolon are treated as a command for MacsBug to execute.

By appending “;g” to the string passed in DebugStr, we cause MacsBug to execute the “g” or “go” command which resumes execution of the suspended application. Since we are going to append this to almost every call to DebugStr (the exceptions being when '\0' or EOT are streamed), we never let the Pascal string in the buffer to grow into the last two bytes of the buffer.

The softflush routine is called when the user streams doutsoftflush (‘\r'). We check to see if there are any characters in the buffer. If there are, we call flushdebugstring, and if there aren’t, we call flushalerts. Since flushdebugstring calls flushalerts, alerts are always flushed.

flushalerts calls SysBeep the number of times specified in alertCount and resets alertCount to zero.

The routine that actually calls DebugStr is flushdebugstring, which is called when the user streams '\n', '\0', or EOT. flushdebugstring takes a single parameter which is used to determine whether or not to append “;g” to the buffer before passing it to DebugStr. After appending the “;g” or not, we flush alerts with a call to flushalerts, call DebugStr, and then zero out the string in the buffer.

Bibliography and References

Information on using the standard C++ iostreams library is readily available. Any recently published work on ANSI C++ would include information on library usage. Implementation is a somewhat different matter. The dout Library would probably not have been possible without:

Plauger, P.J. The Draft Standard C++ Library. Prentice Hall, 1995.

For information on MacsBug:

Apple Computer. MacsBug Reference and Debugging Guide. Addison Wesley, 1990.


Community Search:
MacTech Search:

Software Updates via MacUpdate

OmniPlan 3.0 - Robust project management...
With OmniPlan, you can create logical, manageable project plans with Gantt charts, schedules, summaries, milestones, and critical paths. Break down the tasks needed to make your project a success,... Read more
Yummy FTP 1.11 - FTP/SFTP/FTPS client fo...
Yummy FTP is an FTP + SFTP + FTPS file transfer client which focuses on speed, reliability and productivity. Whether you need to transfer a few files or a few thousand, schedule automatic backups, or... Read more
Tweetbot 2.1 - Popular Twitter client. (...
Tweetbot is a full-featured OS X Twitter client with a lot of personality. Whether it's the meticulously-crafted interface, sounds and animation, or features like multiple timelines and column views... Read more
MacPilot 8.0 - Enable over 1,200 hidden...
MacPilot gives you the power of UNIX and the simplicity of Macintosh, which means a phenomenal amount of untapped power in your hands! Use MacPilot to unlock over 1,200 features, and access them all... Read more
Typinator 6.7 - Speedy and reliable text...
Typinator turbo-charges your typing productivity. Type a little. Typinator does the rest. We've all faced projects that require repetitive typing tasks. With Typinator, you can store commonly used... Read more
Adobe Lightroom 6.2 - Import, develop, a...
Adobe Lightroom is available as part of Adobe Creative Cloud for as little as $9.99/month bundled with Photoshop CC as part of the photography package. Lightroom 6 is also available for purchase as a... Read more
ForeverSave 2.1.4 - Universal auto-save...
ForeverSave auto-saves all documents you're working on while simultaneously doing backup versioning in the background. Lost data can be quickly restored at any time. Losing data, caused by... Read more
VueScan 9.5.27 - Scanner software with a...
VueScan is a scanning program that works with most high-quality flatbed and film scanners to produce scans that have excellent color fidelity and color balance. VueScan is easy to use, and has... Read more
AirPort Utility 6.3.6 - Set up and manag...
Note: Most recent release available only within OS X 10.11 El Capitan update. Use AirPort Utility to set up and manage your Wi-Fi network and AirPort base stations, including AirPort Express, AirPort... Read more
Quicksilver 1.3.1 - Application launcher...
Quicksilver is a light, fast and free Mac application that gives you the power to control your Mac with keystrokes alone. Quicksilver allows you to find what you need quickly and easily, then act... Read more

Super Sharp (Games)
Super Sharp 1.1 Device: iOS Universal Category: Games Price: $1.99, Version: 1.1 (iTunes) Description: Your finger has never been so sharp! Cut with skill to complete the 120 ingenious physics levels of Super Sharp and become a cut... | Read more »
Assembly - Graphic design for everyone...
Assembly - Graphic design for everyone 1.0 Device: iOS Universal Category: Photography Price: $2.99, Version: 1.0 (iTunes) Description: Assembly is the easiest most powerful design tool on the App Store. Create anything you can... | Read more »
YAMGUN (Games)
YAMGUN 1.0 Device: iOS Universal Category: Games Price: $2.99, Version: 1.0 (iTunes) Description: The invasion has begun! Protect the walls of the citadel against waves of enemies! But watch out, you will soon run out of ammo...... | Read more »
Royal Bounty HD (Games)
Royal Bounty HD 1.0 Device: iOS Universal Category: Games Price: $4.99, Version: 1.0 (iTunes) Description: New World Computing Approved "Hi Guys! looks good so far! keep up the good work. I worked on HoMM 3 and 4 creating all of the... | Read more »
Swords & Crossbones: An Epic Pirate...
Swords & Crossbones: An Epic Pirate Story 1.0 Device: iOS Universal Category: Games Price: $4.99, Version: 1.0 (iTunes) Description: | Read more »
Camel Up (Games)
Camel Up 1.0.0 Device: iOS Universal Category: Games Price: $4.99, Version: 1.0.0 (iTunes) Description: | Read more »
The Martian: Bring Him Home (Games)
The Martian: Bring Him Home 1.0 Device: iOS Universal Category: Games Price: $2.99, Version: 1.0 (iTunes) Description: Based on the best selling novel and critically acclaimed film, THE MARTIAN tells the story of Astronaut Mark... | Read more »
This Week at 148Apps: September 21-30, 2...
Leap Into Fall With 148Apps How do you know what apps are worth your time and money? Just look to the review team at 148Apps. We sort through the chaos and find the apps you're looking for. The ones we love become Editor’s Choice, standing out above... | Read more »
Tweetbot 4 for Twitter (Social Networki...
Tweetbot 4 for Twitter 4.0 Device: iOS Universal Category: Social Networking Price: $4.99, Version: 4.0 (iTunes) Description: *** 50% off for a limited time. *** | Read more »
Mori (Games)
Mori 1.0 Device: iOS Universal Category: Games Price: $2.99, Version: 1.0 (iTunes) Description: Stop, rewind and unwind with Mori. Time is always running, take a moment to take control. Mori is an action puzzle game about infinitely... | Read more »

Price Scanner via

Save up to $350 with Apple refurbished iMacs
Apple has Certified Refurbished iMacs available for up to $350 off the cost of new models. Apple’s one-year warranty is standard, and shipping is free: - 27″ 3.5GHz 5K iMac – $1949 $350 off MSRP - 27... Read more
Mac Pros on sale for up to $300 off MSRP
B&H Photo has Mac Pros on sale for up to $300 off MSRP. Shipping is free, and B&H charges sales tax in NY only: - 3.7GHz 4-core Mac Pro: $2818.99, $181 off MSRP - 3.5GHz 6-core Mac Pro: $3699... Read more
5K iMacs on sale for up to $150 off MSRP, fre...
B&H Photo has the 27″ 3.3GHz 5K iMac on sale for $1899.99 including free shipping plus NY tax only. Their price is $100 off MSRP. They have the 27″ 3.5GHz 5K iMac on sale for $2149, $150 off MSRP... Read more
Twelve South Redesigns BookArc For Today’s Sm...
Twelve South has announced a redesigned version of their very first product, BookArc for MacBook. Tailored specifically for the newest generation of MacBooks, BookArc holds the new, smaller Apple... Read more
Phone 6s Tips & Tricks – Tips Book For iP...
Poole, United Kingdom based Tap Guides Ltd. has announced the release and immediate availability of iPhone 6s Tips & Tricks, an in-depth eBook available in the iBookstore that’s priced just $2.99... Read more
13-inch 2.5GHz MacBook Pro on sale for $994,...
Best Buy has the 13″ 2.5GHz MacBook Pro available for $994.99 on their online store. Choose free shipping or free instant local store pickup (if available). Their price is $105 off MSRP. Price valid... Read more
Is The iPad Pro Really A Serious Laptop Repla...
Probably not, at least for productive professionals and other power users. Steve Jobs declared that we’d entered the “post-PC Era” with the advent of the original iPad in 2010, a phrase we don’t hear... Read more
Wednesday Deal: 13-inch Retina MacBook Pros f...
Adorama has 13″ Retina MacBook Pros on sale for up to $130 off MSRP. Shipping is free, and Adorama charges sales tax for NY & NJ residents only: - 13″ 2.7GHz/128GB Retina MacBook Pro: $1199.99 $... Read more
uBar 3.0 for Mac OS X – Custom Dock Replaceme...
Brawer Software has announced the release of uBar 3.0, an important update to their popular app and window manager for Mac OS X. uBar allows users to position it whichever side of the screen they... Read more
13-inch 2.5GHz MacBook Pro (refurbished) avai...
Apple has Certified Refurbished 13″ 2.5GHz MacBook Pros available for $829, or $270 off the cost of new models. Apple’s one-year warranty is standard, and shipping is free: - 13″ 2.5GHz MacBook Pros... Read more

Jobs Board

*Apple* Retail - Multiple Customer Support P...
Job Description:Customer SupportSpecialist - Retail Customer Service and SalesTransform Apple Store visitors into loyal Apple customers. When customers enter the Read more
Software Engineer, *Apple* Watch - Apple (U...
…the team that is revolutionizing the watch! As a software engineer on the Apple Watch team, you will be responsible for building world-class applications and frameworks Read more
*Apple* Online Store UAT Lead - Apple (Unite...
**Job Summary** The Apple Online Store is a fast paced and ever evolving business environment. The User Acceptance Testing (UAT) lead in this organization is able to Read more
Hardware Systems Integration Engineer - *App...
**Job Summary** We are seeking an enthusiastic electrical engineer for the Apple Watch team. This is a design engineering position that entails working with Read more
Touch Validation Design (EE) - *Apple* Watc...
**Job Summary** Help launch next-generation Touch Technologies in Apple products. The Touch Technology team develops cutting-edge Touch solutions and technologies that Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.