Re: Weird Bug Report on 10.5

At 9:17 AM -0800 3/8/10, Brent Smith wrote: >The thing is, im on 10.6, not 10.5. Is my only option to get a dev machine >with 10.5 on it? According to the Internet, some people have had success running 10.5 under VMWare on 10.6. For example:

Re: Weird Bug Report on 10.5

On or about 3/8/10 10:14 AM, thus spake "Steve Bird" : > > On Mar 8, 2010, at 12:49 PM, Matt Neuburg wrote: > >> my experience is that one cannot >> develop reliably for 10.x with a machine running 10.x on which test. > > Maybe change "with" to "without", and I'd agree with you Maybe. Or i

Re: Weird Bug Report on 10.5

On Mar 8, 2010, at 12:49 PM, Matt Neuburg wrote: > my experience is that one cannot > develop reliably for 10.x with a machine running 10.x on which test. Maybe change "with" to "without", and I'd agree with you Steve Bird Cu

Re: Weird Bug Report on 10.5

On Mon, 8 Mar 2010 09:17:51 -0800, Brent Smith said: >The thing is, im on 10.6, not 10.5. Is my only option to get a dev machine with 10.5 on it? That is not a Cocoa question; you should really be raising this on the Xcode list. But if you are just after advice, my experience is that one cannot d

Re: Weird Bug Report on 10.5

On 3/8/10 12:22 PM, Eric Gorr said: >Well, you can partition your HD and install Leopard on the other >partition. There is no need to use a different computer. Not necessarily. Newer Macs only support 10.6. Another option is to run 10.5 (Server) in a virtual machine. -- ___

Re: Weird Bug Report on 10.5

On Mar 8, 2010, at 12:17 PM, Brent Smith wrote: > The thing is, im on 10.6, not 10.5. Is my only option to get a dev machine > with 10.5 on it? What else is different between your machine and the crashed machine? Perhaps it's fast CPU vs. slow. Perhaps it's x86 vs. PPC. > > > On Mar 8, 2

Re: Weird Bug Report on 10.5

On Mon, Mar 8, 2010 at 9:17 AM, Brent Smith wrote: > The thing is, im on 10.6, not 10.5. Is my only option to get a dev machine > with 10.5 on it? If you're supporting 10.5, you should have a 10.5 machine (or at least a bootable volume) at the ready for situations just like this. You have a bug

Re: Weird Bug Report on 10.5

Well, you can partition your HD and install Leopard on the other partition. There is no need to use a different computer. But, yes, your best bet is likely to be able to reproduce the crash yourself. Of course, you could try running your app with Zombies enabled under 10.6. You may be able to s

Re: Weird Bug Report on 10.5

I am doing one NSThread method which basically phones home. However thats in my appDelegate, in the init method, and it only runs once. I cant really see my appDelegate being unallocated when the app starts? On Mar 8, 2010, at 9:12 AM, Dave DeLong wrote: > Like Steve Bird said, it's not your GU

Re: Weird Bug Report on 10.5

The thing is, im on 10.6, not 10.5. Is my only option to get a dev machine with 10.5 on it? On Mar 8, 2010, at 9:06 AM, Eric Gorr wrote: > ooo...good point. I missed that too. > > Problems involving objc_msgSend can usually be caught by reproducing the > crash with zombies enabled. > > > >

Re: Weird Bug Report on 10.5

Like Steve Bird said, it's not your GUI thread that crashed, it's the thread you've created via NSThread. Perhaps it's trying to invoke a selector on a deallocated object or something? Dave On Mar 8, 2010, at 10:05 AM, Brent Smith wrote: > The datasource is being hooked up with bindings and c

Re: Weird Bug Report on 10.5

ooo...good point. I missed that too. Problems involving objc_msgSend can usually be caught by reproducing the crash with zombies enabled. On Mar 8, 2010, at 12:02 PM, Steve Bird wrote: > > On Mar 8, 2010, at 11:57 AM, Brent Smith wrote: > >> I am getting an EXC_BAD_ACCESS on 10.5 only, it w

Re: Weird Bug Report on 10.5

The datasource is being hooked up with bindings and core data. maybe there is something that just doesnt work on 10.5 with bindings and CD? On Mar 8, 2010, at 9:03 AM, Eric Gorr wrote: > You almost certainly have a data source assigned to your table that is being > called as the table is tryin

Re: Weird Bug Report on 10.5

You almost certainly have a data source assigned to your table that is being called as the table is trying to draw itself. Perhaps something has gone wrong in there...? On Mar 8, 2010, at 11:57 AM, Brent Smith wrote: > I am getting an EXC_BAD_ACCESS on 10.5 only, it works fine in 10.6 > > I c

Re: Weird Bug Report on 10.5

On Mar 8, 2010, at 11:57 AM, Brent Smith wrote: > I am getting an EXC_BAD_ACCESS on 10.5 only, it works fine in 10.6 > > I cant seem to deduce the problem b/c its crashing on events that AppKit is > calling, and nothing that I am calling. Notice that it's thread ONE that crashed, not thread ZE