[MacRuby-devel] Setting Breakpoints/Debugger

Eloy Duran eloy.de.enige at gmail.com
Thu Jun 18 00:54:40 PDT 2009


Oh yes that would be a good idea! And fairly “easy” as well, at least  
using plain IRB should be, we just won't get much context information.

Cheerio,
Eloy

On Jun 18, 2009, at 9:47 AM, Matt Aimonetti wrote:

> Like Eloy I do TDD but apparently, unlike him I use the debugger  
> quite often. (Mainly in my specs when I can't get them to pass)
> Not being able to use ruby debug in MacRuby is something that used  
> to really bother me at first. I'm thinking about maybe hacking  
> hotconsole so you could run it in the context of your app. That  
> would obviously not be as nice a real debugger but that might be cool.
>
> - Matt
>
>
> On Thu, Jun 18, 2009 at 12:33 AM, Eloy Duran  
> <eloy.de.enige at gmail.com> wrote:
> Hi Pual,
>
> I sometimes use GDB when I need to debug RubyCocoa/MacRuby  
> _themselves_, as they're written in C. For Ruby code, however,  I  
> almost never need a debugger.
> Maybe it's because I write most code test driven so I know that the  
> code is probably ok when I actually use it. In the cases where it  
> didn't pan out as expected, I use print style debugging or ruby- 
> debug (RubyCocoa). For a more elaborate explanation, please see the  
> testing video of Manfred explaining about it at the Ruby on OS X  
> conference: http://www.fngtps.com/2009/06/ruby-on-os-x-conference-videos
>
> We have a fairly big RubyCocoa app and some of our Rails apps are  
> really big.
>
> It's unfortunate that ruby-debug doesn't work on MacRuby, but  
> Laurent has already announced that at some point in the future work  
> will be done in this area. But at this moment, MacRuby itself still  
> needs lots of work. So we'll need to have a bit more patience for a  
> real debugger.
>
> HTH,
> Eloy
>
>
> On Jun 18, 2009, at 4:42 AM, Paul Howson wrote:
>
> On 04/06/2009, at 6:57 AM, Laurent Sansonetti wrote:
>
> I have an idea about adding facilities inside the new VM in order to  
> attach a debugger to it (and we could even patch gdb to add Ruby  
> support!) but I won't be able to start this any time soon, because  
> there are too many higher priority things to implement first. But if  
> one wants to help... patches are always welcome.
>
> Laurent
>
> Hmmm. Lack of debugger support is surely a serious limitation. A  
> deal-stopper for any complex real-world app I would have thought.
>
> I guess you're aware that this will eventually be needed.
>
> Is anyone using MacRuby for a large project? How are they coping  
> without a debugger? (I'd like to know since I'm planning to convert  
> an old non-Objective-C app to MacRuby).
>
> Paul Howson
> Queensland Australia
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20090618/8c3fa99b/attachment.html>


More information about the MacRuby-devel mailing list