Hey folks, After installing the 'grit' gem I required' it in macirb and received the following: ben@Homeslice ~ Ϟ macirb irb(main):001:0> require 'grit' unrecognized defined? arg: 21 (NODE_AND)fish: Job 1, 'macirb' terminated by signal SIGABRT (Abort) Which, I believe is responding to line 12 in grit.rb – http://github.com/mojombo/grit/blob/master/lib/grit.rb#L 12 Is this a bug that should be logged? I've tried defined? RUBY_ENGINE in macirb and it appears to execute without a problem Cheers, -- Ben Schwarz Web architect Web: http://www.germanforblack.com -- Please consider your environment before printing or distributing this material. --
hmm are you on 0.5 trunk? macgem isn't fully working and require on a gem doesn't work.... However it also fails on trunk: $ macruby -e "require 'rubygems'; gem 'grit'; require 'grit'" unrecognized defined? arg: 21 (NODE_AND)Abort trap Please open a ticket so we can look into it. Thanks, - Matt On Wed, Sep 16, 2009 at 5:01 PM, Ben Schwarz <ben.schwarz@gmail.com> wrote:
Hey folks, After installing the 'grit' gem I required' it in macirb and received the following:
ben@Homeslice ~ Ϟ macirb irb(main):001:0> require 'grit' unrecognized defined? arg: 21 (NODE_AND)fish: Job 1, 'macirb' terminated by signal SIGABRT (Abort)
Which, I believe is responding to line 12 in grit.rb – http://github.com/mojombo/grit/blob/master/lib/grit.rb#L12 Is this a bug that should be logged? I've tried defined? RUBY_ENGINE in macirb and it appears to execute without a problem
Cheers,
--
*Ben Schwarz* *Web architect * * * Web: http://www.germanforblack.com
-- Please consider your environment before printing or distributing this material. --
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi Ben, This is a missing feature in the compiler, in the way we compile the defined? expression. It's easily reproducible here: $ ./miniruby -e 'p (defined? FOO && 42)' unrecognized defined? arg: 21 (NODE_AND)Abort trap I filed a test_vm case. Now, it looks like the code you found this problem is bugged. if defined? RUBY_ENGINE && RUBY_ENGINE == 'jruby' should probably be written as if (defined? RUBY_ENGINE) && RUBY_ENGINE == 'jruby' otherwise, it seems to be the equivalent of if defined?(RUBY_ENGINE && RUBY_ENGINE == 'jruby') which is probably not what the code wants to do. Laurent On Sep 16, 2009, at 5:01 PM, Ben Schwarz wrote:
Hey folks,
After installing the 'grit' gem I required' it in macirb and received the following:
ben@Homeslice ~ Ϟ macirb irb(main):001:0> require 'grit' unrecognized defined? arg: 21 (NODE_AND)fish: Job 1, 'macirb' terminated by signal SIGABRT (Abort)
Which, I believe is responding to line 12 in grit.rb – http://github.com/mojombo/grit/blob/master/lib/grit.rb#L 12 Is this a bug that should be logged? I've tried defined? RUBY_ENGINE in macirb and it appears to execute without a problem
Cheers,
--
Ben Schwarz Web architect
Web: http://www.germanforblack.com
-- Please consider your environment before printing or distributing this material. --
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hey Laurent, Would it be possible for the error thrown to post some line / character information (backtrace?) Or can I turn some verboseness on for debugging these issues somehow? Cheers, Ben On 17/09/2009, at 12:16 PM, Laurent Sansonetti wrote:
Hi Ben,
This is a missing feature in the compiler, in the way we compile the defined? expression.
It's easily reproducible here:
$ ./miniruby -e 'p (defined? FOO && 42)' unrecognized defined? arg: 21 (NODE_AND)Abort trap
I filed a test_vm case.
Now, it looks like the code you found this problem is bugged.
if defined? RUBY_ENGINE && RUBY_ENGINE == 'jruby'
should probably be written as
if (defined? RUBY_ENGINE) && RUBY_ENGINE == 'jruby'
otherwise, it seems to be the equivalent of
if defined?(RUBY_ENGINE && RUBY_ENGINE == 'jruby')
which is probably not what the code wants to do.
Laurent
On Sep 16, 2009, at 5:01 PM, Ben Schwarz wrote:
Hey folks,
After installing the 'grit' gem I required' it in macirb and received the following:
ben@Homeslice ~ Ϟ macirb irb(main):001:0> require 'grit' unrecognized defined? arg: 21 (NODE_AND)fish: Job 1, 'macirb' terminated by signal SIGABRT (Abort)
Which, I believe is responding to line 12 in grit.rb – http://github.com/mojombo/grit/blob/master/lib/grit.rb#L 12 Is this a bug that should be logged? I've tried defined? RUBY_ENGINE in macirb and it appears to execute without a problem
Cheers,
--
Ben Schwarz Web architect
Web: http://www.germanforblack.com
-- Please consider your environment before printing or distributing this material. --
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Would it be possible for the error thrown to post some line / character information (backtrace?) Adding backtrace information is in the TODO list for 0.5.
Or can I turn some verboseness on for debugging these issues somehow? Not currently. I tend to use a lot the following line when searching for a MacRuby bug: STDERR.puts "#{__FILE__}:#{__LINE}"
My understanding is that backtraces are really high on Laurent's TODO list and I also use the same trick as Vincent when I need to debug some of my code. (and yes, it's very frustrating and I can't wait to have some decent backtraces and hopefully a debugger) - Matt On Thu, Sep 17, 2009 at 1:23 AM, Vincent Isambart < vincent.isambart@gmail.com> wrote:
Would it be possible for the error thrown to post some line / character information (backtrace?) Adding backtrace information is in the TODO list for 0.5.
Or can I turn some verboseness on for debugging these issues somehow? Not currently. I tend to use a lot the following line when searching for a MacRuby bug: STDERR.puts "#{__FILE__}:#{__LINE}"
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Awesome stuff lads. Perhaps this could be added to your .irbrc files to have it always present until backtraces are available? On 17/09/2009, at 7:20 PM, Matt Aimonetti wrote:
My understanding is that backtraces are really high on Laurent's TODO list and I also use the same trick as Vincent when I need to debug some of my code. (and yes, it's very frustrating and I can't wait to have some decent backtraces and hopefully a debugger)
- Matt
On Thu, Sep 17, 2009 at 1:23 AM, Vincent Isambart <vincent.isambart@gmail.com
wrote: Would it be possible for the error thrown to post some line / character information (backtrace?) Adding backtrace information is in the TODO list for 0.5.
Or can I turn some verboseness on for debugging these issues somehow? Not currently. I tend to use a lot the following line when searching for a MacRuby bug: STDERR.puts "#{__FILE__}:#{__LINE}"
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hey Ben,
Awesome stuff lads. Perhaps this could be added to your .irbrc files to have it always present until backtraces are available?
That wouldn't do any good though, as __FILE__ and __LINE always point to the file and line of the binding that it's evaluated from. So putting it in .irbrc at line 3 would mean it would print ".irbrc: 3", not what you'd expect… Eloy
On 17/09/2009, at 7:20 PM, Matt Aimonetti wrote:
My understanding is that backtraces are really high on Laurent's TODO list and I also use the same trick as Vincent when I need to debug some of my code. (and yes, it's very frustrating and I can't wait to have some decent backtraces and hopefully a debugger)
- Matt
On Thu, Sep 17, 2009 at 1:23 AM, Vincent Isambart <vincent.isambart@gmail.com
wrote: Would it be possible for the error thrown to post some line / character information (backtrace?) Adding backtrace information is in the TODO list for 0.5.
Or can I turn some verboseness on for debugging these issues somehow? Not currently. I tend to use a lot the following line when searching for a MacRuby bug: STDERR.puts "#{__FILE__}:#{__LINE}"
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Good point Eloy, I wasn't really thinking there... On 17/09/2009, at 7:55 PM, Eloy Duran wrote:
Hey Ben,
Awesome stuff lads. Perhaps this could be added to your .irbrc files to have it always present until backtraces are available?
That wouldn't do any good though, as __FILE__ and __LINE always point to the file and line of the binding that it's evaluated from. So putting it in .irbrc at line 3 would mean it would print ".irbrc: 3", not what you'd expect…
Eloy
On 17/09/2009, at 7:20 PM, Matt Aimonetti wrote:
My understanding is that backtraces are really high on Laurent's TODO list and I also use the same trick as Vincent when I need to debug some of my code. (and yes, it's very frustrating and I can't wait to have some decent backtraces and hopefully a debugger)
- Matt
On Thu, Sep 17, 2009 at 1:23 AM, Vincent Isambart <vincent.isambart@gmail.com
wrote: Would it be possible for the error thrown to post some line / character information (backtrace?) Adding backtrace information is in the TODO list for 0.5.
Or can I turn some verboseness on for debugging these issues somehow? Not currently. I tend to use a lot the following line when searching for a MacRuby bug: STDERR.puts "#{__FILE__}:#{__LINE}"
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
participants (5)
-
Ben Schwarz
-
Eloy Duran
-
Laurent Sansonetti
-
Matt Aimonetti
-
Vincent Isambart