From: Scott Barron <linguist@...>
Date: 2008-01-25T05:25:41+09:00
Subject: Re: DTrace segfaults on Leopard

------=_Part_25421_3625531.1201206341343
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Jan 24, 2008 10:26 AM, Juan Mat=EDas <jmrepetti@gmail.com> wrote:

> I have just read this article, maybe could help you.
> Apple Crippled Its DTrace Port:
> http://developers.slashdot.org/article.pl?sid=3D08/01/22/2156244
>
> Juan Mat=EDas Repetti.
>
> On Jan 24, 2008 1:12 PM, Dane Jensen <careo@fastmail.fm> wrote:
>
> >
> > On Jan 17, 2008, at 2:09 PM, Wincent Colaiuta wrote:
> >
> > > I'd like to use DTrace on Leopard to do some profiling of a Ruby app
> > > but I'm finding that any script that uses the "object-free" probe
> > > eventually leads to a segfault.
> >
> > [snip]
> >
> > > Needless to say, I can't run the application that I'd like to profile
> > > either. The same crashes occur when trying to use the "object-free"
> > > probe from inside Apple's Instruments GUI.
> > >
> > > Can anybody else repro this or is there something fishy with my
> > > system?
> > >
> > > Cheers,
> > > Wincent
> >
> > I can reproduce it every time. Happens without fail.
> >
> > Kind of makes it useless for watching object creation and deletion,
> > huh? :)
> >
> > Have you had any luck getting it to work?
> >
> > -Dane
> >
> >
>

Apple's modifications to DTrace aren't the issue here - it's a bug in the
Ruby patch, which would be my fault.  I can reproduce it and I'm looking
into a fix.  I can release a new ruby patch with the fix but I'll have to
defer to the Apple guys to see how they want to handle OSX's ruby.

-Scott

------=_Part_25421_3625531.1201206341343--