After painstakingly going through my code line by line, I managed to find the issue. I was using a custom NSScroller subclass, and the rect returned by rectForPart: was an empty rect, which caused NSBezierPath to freak out. The sanity check is a good idea, but a) the log message should provide info, b) it shouldn't be impossible to track down with the debugger, and c) it shouldn't break the whole app! I'm hesitant on filing a bug for this because it appears that there is no such check on *later* versions of OS X ;-)
On 2011-05-05, at 7:17 PM, Kyle Sluder wrote: > On Thu, May 5, 2011 at 5:49 PM, Indragie Karunaratne > <cocoa...@indragie.com> wrote: >> I will check my NSBezierPath code to see if I'm doing anything of that sort, >> but like I said, this only happens on 10.6.7. And Kyle, indeed the only code >> of mine that is in the stack trace is NSApplicationMain(). The stack trace >> confirms this: >> thread #1: tid = 0x2d03, stop reason = breakpoint 1.1 >> frame #0: 0x00007fff885b0a34 Foundation`NSLog >> frame #1: 0x00007fff86ad758b AppKit`-[NSApplication run] + 651 >> frame #2: 0x00007fff86ad01a8 AppKit`NSApplicationMain + 364 > > Another dumb question: are you sure this NSLog you're breaking on is > the one complaining about NSBezierPath? It seems very odd for > -[NSApplication run] to call NSLog to complain about NSBezierPath > directly. There should be intervening stack symbols—I find it unlikely > that all of them have been tail-call optimized away. > > --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
