Comments on: The glorious life of a bug killer http://blog.clickablebliss.com/2010/01/15/the-glorious-life-of-a-bug-killer/ Cocoa, Rails and User Interface commentary. Thu, 26 Jan 2012 16:10:21 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Mike Zornek http://blog.clickablebliss.com/2010/01/15/the-glorious-life-of-a-bug-killer/comment-page-1/#comment-110322 Mike Zornek Tue, 19 Jan 2010 02:02:01 +0000 http://blog.clickablebliss.com/?p=305#comment-110322 <p>Thanks for the tips Mike. I used em a bit tonight and eventually tripped over the issue (colliding category methods only on 10.6). Hope to post more about the issue on the blog soon.</p> Thanks for the tips Mike. I used em a bit tonight and eventually tripped over the issue (colliding category methods only on 10.6). Hope to post more about the issue on the blog soon.

]]> By: mikeash http://blog.clickablebliss.com/2010/01/15/the-glorious-life-of-a-bug-killer/comment-page-1/#comment-110196 mikeash Sat, 16 Jan 2010 16:08:38 +0000 http://blog.clickablebliss.com/?p=305#comment-110196 <p>Well, that NUL didn't quite come out right. The thing in the single quotes in the parentheses is supposed to be a backslash-zero.</p> Well, that NUL didn’t quite come out right. The thing in the single quotes in the parentheses is supposed to be a backslash-zero.

]]> By: mikeash http://blog.clickablebliss.com/2010/01/15/the-glorious-life-of-a-bug-killer/comment-page-1/#comment-110195 mikeash Sat, 16 Jan 2010 16:07:07 +0000 http://blog.clickablebliss.com/?p=305#comment-110195 <p>Sounds like your string contains a NUL ('') character around the 70 character point. NSString is perfectly happy to contain NUL characters, and it does no harm there. However, the moment that you convert it to a C string, for example when printing it in the debugger, that NUL character will be interpreted as a string terminator, and your output will be truncated. It will not only truncate debug printing, but anything else that goes through a C string, like filesystem paths, and possibly whatever you're using to post your HTTP request.</p> <p>To help with debugging, I recommend printing [string dataUsingEncoding: NSUTF8StringEncoding] for this case. The output is not as readable, but it will show the entire string, including any NUL characters.</p> Sounds like your string contains a NUL (”) character around the 70 character point. NSString is perfectly happy to contain NUL characters, and it does no harm there. However, the moment that you convert it to a C string, for example when printing it in the debugger, that NUL character will be interpreted as a string terminator, and your output will be truncated. It will not only truncate debug printing, but anything else that goes through a C string, like filesystem paths, and possibly whatever you’re using to post your HTTP request.

To help with debugging, I recommend printing [string dataUsingEncoding: NSUTF8StringEncoding] for this case. The output is not as readable, but it will show the entire string, including any NUL characters.

]]>