[MacRuby-devel] backtrace in cocoa callbacks ...

[Robert Rice]

Hi Steven:

I've noticed that my backtraces (when I get them) are often incomplete. Some method calls will be missing from the backtrace. But I'm more concerned that some errors, e.g., undefined method names, will often cause a loop that I can't catch. And if I don't kill it quickly enough it will use up memory until the Finder crashes requiring a hard reset. This can make debugging difficult. I assume that the looping occurs somewhere searching the Cocoa object inheritances.

My experience thus far indicates that MacRuby will be fast enough for many large applications, but I don't think it will be widely accepted until it is robust enough to catch most errors so that they can be dealt with.

After viewing the introduction to Xcode 4 and LLVM, I am curious if MacRuby compiler could be integrated into and directly compiled by LLVM. LLVM claims to have much improved diagnostics and an enviable analysis phase. Is this idea on the MacRuby roadmap?

Bob Rice


On Sep 14, 2010, at 5:36 PM, Steven Parkes wrote:

> I guess the question is, do they (backtrace in cocoa/framework callbacks) ever work? Since everything in a cocoa is basically a callback, if they don't ... it makes things tough (for me, at least). I get the exceptions and I can catch/rescue them, but the backtraces seem always to be empty when I'm running in a Cocoa callback like -applicationDidFinishLaunching.
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>