Home     |     .Net Programming    |     cSharp Home    |     Sql Server Home    |     Javascript / Client Side Development     |     Ajax Programming

Ruby on Rails Development     |     Perl Programming     |     C Programming Language     |     C++ Programming     |     IT Jobs

Python Programming Language     |     Laptop Suggestions?    |     TCL Scripting     |     Fortran Programming     |     Scheme Programming Language


 
 
Cervo Technologies
The Right Source to Outsource

MS Dynamics CRM 3.0

Ruby Programming Language

Bus error / abort trop with latest sources


Hello,

I'm compiling Ruby 1.9 from the SVN tree, latest changeset is 12384 on
OS
X/PPC 10.4.9.

It fails during compilation with the following message:

..
gcc -O -pipe -pipe -fno-common  -L.    main.o  libruby-static.a
-lpthread -ldl -lobjc   -o miniruby
: -- stack frame ------------
0000 (0x126000): 00000000 <- lfp <- dfp
-- control frame ----------
c:0001 p:---- s:0001 b:-001 l:000000 d:000000 ------
---------------------------
[BUG] Bus Error
ruby 1.9.0 (2007-05-25) [powerpc-darwin8.9.0]

Running miniruby and pressing ^D leads to the same message. miniruby -v,
same.

Am I the only one? I've tried make clean, rerunning configure, changing
-O2
into -O, no success.

Thanks.

--
Posted via http://www.ruby-forum.com/.

Hi,

At Fri, 25 May 2007 21:43:54 +0900,
Ollivier Robert wrote in [ruby-talk:252956]:

> It fails during compilation with the following message:

> ...
> gcc -O -pipe -pipe -fno-common  -L.    main.o  libruby-static.a
> -lpthread -ldl -lobjc   -o miniruby
> : -- stack frame ------------
> 0000 (0x126000): 00000000 <- lfp <- dfp
> -- control frame ----------
> c:0001 p:---- s:0001 b:-001 l:000000 d:000000 ------
> ---------------------------
> [BUG] Bus Error
> ruby 1.9.0 (2007-05-25) [powerpc-darwin8.9.0]

What command failed?

> Running miniruby and pressing ^D leads to the same message. miniruby -v,
> same.

It's a known bug.

Index: compile.c
===================================================================
--- compile.c   (revision 12384)
+++ compile.c   (working copy)
@@ -145,5 +145,8 @@ rb_iseq_compile(VALUE self, NODE *node)
     GetISeqPtr(self, iseq);

-    if (nd_type(node) == NODE_SCOPE) {
+    if (node == 0) {
+       COMPILE(ret, "nil", node);
+    }
+    else if (nd_type(node) == NODE_SCOPE) {
        /* iseq type of top, method, class, block */
        set_local_table(iseq, node->nd_tbl);
@@ -198,7 +201,4 @@ rb_iseq_compile(VALUE self, NODE *node)
            COMPILE(ret, "defined guard", node);
        }
-       else if (node == 0) {
-           COMPILE(ret, "nil", node);
-       }
        else {
            rb_bug("unknown scope");

--
Nobu Nakada

In article <200705251323.l4PDN9LZ005@sharui.nakada.kanuma.tochigi.jp>,
Nobuyoshi Nakada  <n@ruby-lang.org> wrote:

>What command failed?

My guess is that it is miniruby which fails.

>> Running miniruby and pressing ^D leads to the same message. miniruby -v,
>> same.

>It's a known bug.

Is it committed in trunk?

Any news on the bug where trying to use "-r debug" does not work because a hook is not yet available (according to ko1)?  I can not switch (and therefore test) 1.9 is the debugger is not usable...

Thanks.

--
Ollivier ROBERT     -=-  Eurocontrol EEC/RIF/SEU  -=-
Systems Engineering Unit

Hi,

At Wed, 30 May 2007 23:15:09 +0900,
Ollivier Robert wrote in [ruby-talk:253586]:

> >What command failed?

> My guess is that it is miniruby which fails.

Yes, obviously.  What I asked is what miniruby was about to do.

> >> Running miniruby and pressing ^D leads to the same message. miniruby -v,
> >> same.

> >It's a known bug.

> Is it committed in trunk?

Yes.

Sat May 26 00:38:21 2007  Nobuyoshi Nakada  <n@ruby-lang.org>

        * eval.c (ruby_exec_internal): do nothing if no code.

        * compile.c (rb_iseq_compile): check node if NULL before check
          nd_type.  [ruby-talk:252956]

> Any news on the bug where trying to use "-r debug" does not
> work because a hook is not yet available (according to ko1)?
> I can not switch (and therefore test) 1.9 is the debugger is
> not usable...

Thank you, I've investigated it, and will fix it.

--
Nobu Nakada

Add to del.icio.us | Digg this | Stumble it | Powered by Megasolutions Inc