>>>>> In <20110620110339.63b2d...@gmail.com> >>>>> "Suraj N. Kurapati" <sun...@gmail.com> wrote: Hi Suraj.
Thank you for you response. > Please try with rspec version 1.1.4 (released May 26, 2008). I tried rspec version 1.1.4 . It seemed that test result was correct. then, I tried with no PROTOTYPE, 'rake vsim'. but, segmentation error occured. follows are message. ** Fatal: (SIGSEGV) Bad pointer access. Closing vsimk. ** Fatal: vsimk is exiting with code 211. (Exit codes are defined in the ModelSim messages appendix of the ModelSim User's Manual.) # SystemExit: exit # from ** /home/kazunori/.gem/ruby/1.8/gems/ruby-vpi-21.1.0/lib/ruby-vpi/core/callback.rb:73:in ** `user_data' # from ** /home/kazunori/.gem/ruby/1.8/gems/ruby-vpi-21.1.0/lib/ruby-vpi/core/callback.rb:73:in ** `relay_verilog' # from ** /home/kazunori/.gem/ruby/1.8/gems/ruby-vpi-21.1.0/lib/ruby-vpi/core/scheduler.rb:103:in ** `advance_to_read_only_slot' # from ** /home/kazunori/.gem/ruby/1.8/gems/ruby-vpi-21.1.0/lib/ruby-vpi/core/scheduler.rb:29:in `initialize' when I tried gplcver, no errors appeared. so I think vsim.so has problem. if I have a time, I'll tackle this issue. > Are you interested in maintaining or developing Ruby-VPI? I have > done more experiments, such as using ucontext instead of pthread[1], > and have more ideas, such as replacing `rake vsim` with a > ruby-vpi.so that can be loaded into any simulator and invoked > on-demand from a C program, and other ideas written in my notebook. That's interesting. I'm sorry but I just returned to school. because of illness. but, I'm really interested in Ruby-VPI. when my condition gets better, I want to join development. -- Kazunori Kimura
