From: Chris M. <ch...@oc...> - 2007-11-29 19:24:30
|
Puts $RUBYCOCOA_DEBUG = true in your app somewhere and have a look at the output, that should give you more of a pointer to what's actually going wrong. Cheers, Chris On 29 Nov 2007, at 17:28, Pierce T. Wetter III wrote: > > So I've had a crashing bug in rubycocoa upon starting my app from > trunk since about the time Leopard shipped. (way before it gets to > actually running my code, it buserrors making a ruby subclass of > NSObject. ) > > Users are grumping at me, so I'm willing to dig into it, but since > its not my code, I'd prefer to debug it at the source level. > Presumably there's some magic incantation to get XCode to find the > RubyCocoa source from where I've checked it out, but I don't know what > it is. > > So what are the steps you have to do so that XCode can debug both > your app and RubyCocoa? > > 1. Does it require me to build rubycocoa in any special way? > > 2. Do I have to tell XCode where to look for the source files after > that? I notice that 0.13 tries to find them on Laurent's hard drive, > which is why I think #1 might apply... > > > Pierce > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |