thanks for the info.

While I know of the gstack underflow for some time now - and that it 
is usually also caused if more than one CGContextRestoreGState() is 
called per CGContextSaveGState(), I've been unable to find any 
unbalanced CGContextSaveGState() / CGContextRestoreGState() calls in 
my code, leaving me with the conclusion that this thing must be 
happening somewhere in Apple's code. It's absolutely harmless, though.

The doClip message was a bug where Remote Buddy called 
CGContextClipToPath() twice in a row - I've fixed that and it should 
no longer occur with the next version.

Best regards, 
Felix