oops, the comment "// crashes here" in the code below should have been on the next line -- the release.
- Larry
Begin forwarded message:
<x-tabstops>28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;From: </x-tabstops><x-tabstops>28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;Larry Campbell <Larry.Campbell@akamai.com></x-tabstops><x-tabstops>28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;
Date: Thu Jan 18, 2001 10:34:17 AM US/Eastern
To: bug-gnustep@gnu.org
Subject: NSLock bug?
X-Mailer: Apple Mail (2.343)
> This seems to be a bug, just wanted to know if maybe it's already fixed in a later
> distribution of either GNUstep or gcc.
>
> This trivial program:
>
> #import <Foundation/Foundation.h>
>
> main()
> {
> NSLock *theLock;
> NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
>
> theLock = [[NSLock alloc] init];
> [theLock lock];
> [theLock unlock]; // crashes here
> [theLock release];
>
> [pool release];
> }
>
> Crashes when releasing the lock with:
>
> Uncaught exception NSLockException, reason: invalid mutex
>
> This is on Redhat Linux 2.2.12. I'm using gcc version egcs-2.91.66 and GNUstep core
> libraries version 0.6.6.
>
> I'm perfectly willing to believe I just need a new gcc or Linux but it would be nice to know
> exactly what I need before flailing around upgrading everything in sight.
>
> Thanks!
>
> - Larry
>
>
</x-tabstops>
- NSLock bug?, Larry Campbell, 2001/01/18
- Fwd: NSLock bug?,
Larry Campbell <=