search for: norbye

Hi there, I''m working on Ruby support for NetBeans, and we''re bundling RSpec (along with JRuby). One thing I''d really like to fix is having content assist (code completion / intellisense / code insight, it has many names) work inside your spec files such that you can not only hit ctrl-space and see "describe", "before", "it" etc.

I have been using iosoop script (see http://www.opensolaris.org/os/community/dtrace/scripts/) written by Brendan Gregg to look at the IO operations of my application. When I was running my test-program on a UFS filesystem I could see both read and write operations like: UID PID D BLOCK SIZE COMM PATHNAME 203803 4436 R 6016592 16384 diskio <none> 203803 4436 W 3448432

If I have the following definition: provider foo { probe bar(const char*); }; and creates the headerfile (snv 43) with dtrace -h I get: extern void __dtrace_foo___bar(char *); This is a "problem" for me (ok, I could add an explicit cast each time I fire the probe, or edit the generated headerfile by hand...), since it generates compilation errors when I call the probe in a C++

I have inserted some probes in my application, and it works great in the "debug build" I have been using. So I wanted to look at the "overhead" introduced by inactive dtrace probes in my application. I am using the Sun Studio 11 compiler, so I added the following options: -xO5 -g0 -xbuiltin But this breaks the linking of my application. Undefined first

It looks like the lates NetBeans milestone can run RSpec specifications: http://wiki.netbeans.org/wiki/view/NewAndNoteWorthyMilestone9 I haven''t tried it myself, but if anyone else does please tell us about your experience. Aslak

How? I have a project full of gems etc etc how can I move it in 3rdRail? I hope I don''t have to do it manually for every single file.. any help appreciated --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

I am currently working on adding DTrace probes we have for Memcached 1.2.5 to the new binary protocol in 1.3 branch. The problem I am facing is that I should have had a new variable into the probe. When we added the probes, all memcached keys would be zeroterminated ascii strings, but in the binary protocol it may not be zero-terminated. So what do I do? According to