Re: No current point for control point bounds
Re: No current point for control point bounds
- Subject: Re: No current point for control point bounds
- From: Indragie Karunaratne <email@hidden>
- Date: Thu, 05 May 2011 19:22:27 -0600
I'm assuming it is, because as soon as I click "Continue" after it breaks, the message is logged. Once the message has been logged once, the entire window stops responding and any attempt to click on anything will just result in the message being logged over and over again.
On 2011-05-05, at 7:17 PM, Kyle Sluder wrote:
> On Thu, May 5, 2011 at 5:49 PM, Indragie Karunaratne
> <email@hidden> 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 (email@hidden)
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:
This email sent to email@hidden