FWIW, I have a lots of stuff built that does work, that makes it easy (for my
needs, anyway) to link to existing ObjC and C++ libraries and quickly prototype
a cocoa UI. I have a bunch of rake tasks that can build cocoa app bundles with
only dylibs, bundles, and the main mach binary, including v
As a quick follow up, I realized that since the focus of my macruby stuff is
cocoa apps which I compile into mach executables avoiding the macruby
executable, I have the opportunity to (and, actually, must) add the custom
sqlite there. Doesn't work for CLI apps that run against macruby, but thos
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 wi
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
Hi Laurent:
Thanks for your reply.
I created a scaled down version of my app using the same print mechanism and it
didn't reproduce the problem.
Rebuilding the app into a new project did not eliminate the problem.
The problem doesn't cause my app to crash, just error messages for the invalid
g
> I'm not even sure loading the sqlite3 macports version first is a good idea,
> since CFNetwork might not work with that version.
Yeah, I thought about that. One would hope that sqlite3 is pretty
consistent/upgradable within minor versions at this point, but there's no
guarantee. One could tr
