Hello all,
I am developing Dtrace Support on JRUby as my GSOC project. In my project I
am planning to add following DTrace probes to JRuby.
· 1. Object-create -: fired when an object is about to allocated
· 2. Array-create -: fired when an Array is about to be allocated
· 3.
Why isn't it possible to pass byte[] back to JRuby DRb server? I believe
it should be passed by reference, right?
Here's an example code:
server.rb
require 'drb/drb'
class Service
def to_java_bytes(str)
str.to_java_bytes
end
def from_java_bytes(bytes)
String.from_java_bytes byte
if I extend the byte[] with DRb::DRbUndumped it works but I get a
warning in the server application:
server.rb:9 warning: singleton on non-persistent Java type
# (http://wiki.jruby.org/Persistence)
Em 16-07-2013 07:44, Rodrigo Rosenfeld Rosas escreveu:
Why isn't it possible to pass byte[] bac
You should be able to find several of these in classes with obvious names
(RubyObject, RubyArray, RubyException, etc) here
https://github.com/jruby/jruby/tree/master/core/src/main/java/org/jruby
To understand more about JRuby internals, there are some good presentation
slides here
http://www.slide
FYI, last I checked (and much to my dismay) custom dtrace providers don't
work on the MacOSX JVM. I would assume it's the same on FreeBSD, though I
haven't tried that.
On Jul 16, 2013 2:25 AM, "Chamila Wijayarathna"
wrote:
> Hello all,
> I am developing Dtrace Support on JRUby as my GSOC project
I've just published an article on how I'm using DRb to command JRuby
from MRI:
http://rosenfeld.herokuapp.com/en/articles/ruby-rails/2013-07-16-running-java-from-mri-ruby-through-drb
I'd appreciate any feedbacks on how to avoid the mentioned warning,
since I need to include that DRb::DRbUndump
Ok, so I think we should defer on the object allocation ones for now
and focus on a few that are coarse-grained and general purpose.
Thoughts below.
On Tue, Jul 16, 2013 at 2:25 AM, Chamila Wijayarathna
wrote:
> · 1. Object-create -: fired when an object is about to allocated
>
> ·
I was wondering we can alias existing dtrace probes or make filters on
existing dtrace probes with names we want. The internal JVM probes would
be nice to have JRuby equivalent names
-Tom
On Tue, Jul 16, 2013 at 3:07 PM, Charles Oliver Nutter
wrote:
> Ok, so I think we should defer on the
