[haiku-bugs] Re: [Haiku] #5321: vm_soft_fault while compiling ruby, reproducible.

  • From: "augiedoggie" <trac@xxxxxxxxxxxx>
  • Date: Sat, 30 Jan 2010 18:46:27 -0000

#5321: vm_soft_fault while compiling ruby, reproducible.
---------------------------+------------------------------------------------
 Reporter:  kallisti5      |       Owner:  axeld    
     Type:  bug            |      Status:  new      
 Priority:  normal         |   Milestone:  R1       
Component:  System/Kernel  |     Version:  R1/alpha1
 Keywords:                 |   Blockedby:           
 Platform:  All            |    Blocking:           
---------------------------+------------------------------------------------

Comment(by augiedoggie):

 Replying to [comment:14 kallisti5]:
 > Replying to [comment:13 augiedoggie]:
 > > Replying to [comment:7 kallisti5]:
 > > > ok.. weird but good news.  compiling ruby (same code) on R1A1 brings
 up the gdb crash window at the same step that was failing in r35267.
 > >
 > > Probably not related to the compile problem in this ticket, just
 wanted to point out that ruby doesn't run on R1A1 because of pthread
 problems that were fixed in r33779
 >
 > As stated this is r35267.

 Yes, but the Version field on this ticket states R1/alpha1 and your
 comment said you were attempting to compile on R1A1 in addition to r35267

 > > There is also a ruby package available for download at [http://www
 .haiku-ports.de/packages/dev-lang/ruby/ruby-1.9.1-x86-gcc2-2009-10-28.zip
 HaikuPorts]
 > >
 > > And the [http://ports.haiku-files.org/wiki/dev-lang/ruby/1.9.1/1
 portlog]
 >
 > Ha... i wish i knew about these.. several of the things in that patch I
 did myself and submitted upstream to Ruby. (they were all added)
 >
 > * changing BEOS defines to defined __HAIKU__  -- checked in
 http://redmine.ruby-lang.org/repositories/diff/ruby-19?rev=26398


 Yes I saw that.  I'm still debating whether to submit a follow up patch to
 fix some of the things you had them change.  You enabled old BeOS code
 paths that were not necessary on Haiku.  They probably won't hurt except
 that we now have to maintain code that is different from other operating
 systems(like library/symbol loading, chown/chgrp stuff, and possibly the
 file IO stuff).  As you can see from the test results in the portlog I
 didn't need to use any of the old BeOS code that you've enabled.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/5321#comment:16>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: