On Fri, Dec 18, 2009 at 3:15 PM, PCWiz wrote:
> Thanks, that's helpful to know.
>
> Kai, I am developing on Snow Leopard but I'm using the 10.5 SDK, so is it
> possible that NSRecursiveLock is being used in NSOperationQueue? Or should I
> set a breakpoint on [NSRecursiveLock alloc] to see where
Thanks, that's helpful to know.
Kai, I am developing on Snow Leopard but I'm using the 10.5 SDK, so is it
possible that NSRecursiveLock is being used in NSOperationQueue? Or should I
set a breakpoint on [NSRecursiveLock alloc] to see where its being allocated?
Independent Cocoa Developer, Macat
On Dec 17, 2009, at 6:26 PM, PCWiz wrote:
> But I'm happy to say that I eventually found the cause of my problem. One of
> the frameworks I was using was compiled using "i386 ppc" set as the
> architecture. Setting this to "Standard (32-bit/64-bit Universal)" and
> recompiling the framework fix
On 18.12.2009, at 15:54, PCWiz wrote:
> Yeah I definitely need to squash this bug. But as Greg Parker said,
> @synchronized (which I'm using) has nothing to do with NSRecursiveLock. And
> the only other threading related classes I'm using are NSOperationQueue and
> NSInvocationOperation. Would
Yeah I definitely need to squash this bug. But as Greg Parker said,
@synchronized (which I'm using) has nothing to do with NSRecursiveLock. And the
only other threading related classes I'm using are NSOperationQueue and
NSInvocationOperation. Would one of these classes use NSRecursiveLock? I am
Great you found this issue.
But according to the log output, it seems that you do have a serious
threading-related problem. I wouldn’t ignore this, it may raise its head any
time in the future and bite you badly.
Good luck
Kai
On 18.12.2009, at 03:26, PCWiz wrote:
> Thanks, will do.
>
> And
Thanks, will do.
And regarding Jeremy's note about the 2 libraries can't be loaded, those are
Input Manager plugins that have nothing to do with my app.
But I'm happy to say that I eventually found the cause of my problem. One of
the frameworks I was using was compiled using "i386 ppc" set as t
On Dec 17, 2009, at 8:55 AM, Jens Alfke wrote:
> On Dec 16, 2009, at 10:04 PM, PCWiz wrote:
>> I'm not using NSLock or NSRecursiveLock directly. I'm using @synchronized on
>> an object that multiple threads acess, to allow only one thread to access
>> the object at a time.
>
> The fact that the
On Dec 16, 2009, at 10:04 PM, PCWiz wrote:
> I'm not using NSLock or NSRecursiveLock directly. I'm using @synchronized on
> an object that multiple threads acess, to allow only one thread to access the
> object at a time.
The fact that the description of the lock is "
'(null)'" makes me suspe
On 16 Dec 2009, at 04:05, PCWiz wrote:
> Here's the screen capture that demonstrates this issue:
>
> http://www.vimeo.com/8208563
>
> This time around, I got a few errors logged in Console:
>
> *** -[NSRecursiveLock unlock]: lock ( '(null)')
> unlocked from thread which did not lock it
> ***
I'm not using NSLock or NSRecursiveLock directly. I'm using
@synchronized on an object that multiple threads acess, to allow only
one thread to access the object at a time.
That said, I only ever got those errors once but in any case I've set
a breakpoint for _NSLockError to trap it next ti
On Dec 15, 2009, at 8:05 PM, PCWiz wrote:
> *** -[NSRecursiveLock unlock]: lock ( '(null)')
> unlocked from thread which did not lock it
> *** Break on _NSLockError() to debug.
> *** -[NSRecursiveLock finalize]: lock ( '(null)')
> finalized while still in use
> *** Break on _NSLockError() to de
I've sent Joar the source off list, but meanwhile I tried Kyle Sluder's
suggestion to run gdb on the app. Here's the log:
pcwiz-mbp:~ Indragie$ gdb
/Users/pcwiz/Desktop/TwitMenu/build/Release/TwitMenu.app
GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul 3 01:19:56 UTC 2009)
Copyright
On 16 dec 2009, at 07.04, PCWiz wrote:
> This is making absolutely 0 sense to me, and right now it seems like its a
> screwup on Xcode's part. I can privately email the source if necessary (its a
> commercial app, but right now I'm willing to do anything to get this fixed).
That doesn't make
Ok, this just got even weirder.
When I launch the app in Release mode from Xcode, something strange happens.
*2* instances of the app are opened. Both instances work fine however.
Now when I launch the Release app from Finder, 2 instances are opened once
again. However this time, one instance o
Hi Joar,
Thanks for the reply.
What I did to add the frameworks was add the frameworks to my Linked Frameworks
and created a new Copy Build phase (target was the Frameworks folder) and then
added the frameworks to that phase.
I checked out the link and it tells me to set the Installation Build
On 15 dec 2009, at 16.48, PCWiz wrote:
> I have 2 frameworks set in a Copy Files build phase and both are being copied
> as they should.
So you intend for your frameworks to be copied into and used from the bundle of
your app? If so, have you set their Installation Directory build setting to
On Tue, Dec 15, 2009 at 8:47 PM, PCWiz wrote:
> Is there any way to do this using one mac?
Yes, just launch Terminal, cd to YourAppBundle.app/Contents/MacOS, and
run gdb from there. Read the gdb manual, tutorials online, and TN2124
for more. http://developer.apple.com/mac/library/technotes/tn20
Is there any way to do this using one mac?
On 2009-12-15, at 9:33 PM, Eric Schlegel wrote:
>
> On Dec 15, 2009, at 8:05 PM, PCWiz wrote:
>
>> This would explain my apps screwup. If it can't connect then that would
>> explain the request timed out and authentication errors. The problem is, I
>
On Dec 15, 2009, at 8:05 PM, PCWiz wrote:
> This would explain my apps screwup. If it can't connect then that would
> explain the request timed out and authentication errors. The problem is, I
> have no idea why this only happens on the Release config *when launched from
> Finder*
>
> And I d
Here's the screen capture that demonstrates this issue:
http://www.vimeo.com/8208563
This time around, I got a few errors logged in Console:
*** -[NSRecursiveLock unlock]: lock ( '(null)')
unlocked from thread which did not lock it
*** Break on _NSLockError() to debug.
*** -[NSRecursiveLock unl
I have 2 frameworks set in a Copy Files build phase and both are being copied
as they should. I haven't explicitly set any command line arguments for the
app, but where would I check that? And nothing is being logged into the Console.
I'll make a quick screen capture right now to demonstrate wha
On Tue, Dec 15, 2009 at 4:34 PM, PCWiz wrote:
> I don't know why this is happening. I don't think its an issue with my code
> if it works in Debug (Xcode & Finder) and Release (Xcode only).
Two rules of software development:
Rule 1: Check again. It's probably your fault.
Rule 2: It's still proba
In Xcode, are you running the target's executable with any command line
arguments?
Kiel
On 16/12/2009, at 11:34 AM, PCWiz wrote:
> I'm having a *really* strange issue here. First of all, my app works fine in
> Debug mode. I can launch it from Xcode or from Finder and it will work fine.
>
> Th
On 16/12/2009, at 11:34 AM, PCWiz wrote:
> My build configurations for both Debug and Release are identical (I haven't
> checked thoroughly, but I know I didnt change much). Both configs are set to
> use the LLVM GCC 4.2 compiler, and GC is set to Required. The only other
> change I've made is
25 matches
Mail list logo
