On Sat, Sep 20, 2008 at 7:57 AM, Mike Gerdts <[EMAIL PROTECTED]> wrote: > On Fri, Sep 19, 2008 at 9:31 PM, Mike Gerdts <[EMAIL PROTECTED]> wrote: >> I still think that it would be a good idea for dtri.o to not read >> environment variables after the application has had a chance to mess >> with the environment. Even if this is fixed, existing applications >> would need to be relinked with the new drti.o to see the fix. I have >> filed a bug report - perhaps someone at Sun can post the bug ID to the >> list as I will not see it until someone at Sun starts to update it. > > I have developed and tested a fix (attached). If someone can get me > the CR ID, I will file drop some mail to request-sponsor to get it > integrated.
A short while after I sent the above message, I lost the zpool that had my build environment in it. Hint: don't use VirtualBox's SAS driver. As Chad Lewis replied, a bug ID was assigned: http://bugs.opensolaris.org/view_bug.do?bug_id=6750659 Anyway, I noticed that this was bumped to Priority 2 (High) a couple days ago. Since I had the fix ready to go and I had been wanting to play with the OpenSolaris build farm[1], I figured it would be a good thing for me to go after. I have sent mail to request-sponsor[2] and am awaiting a reply. 1.http://test.opensolaris.org/testfarm/index.jsp 2.http://mail.opensolaris.org/pipermail/request-sponsor/2008-November/003989.html I've done a build of onnv_102 (in just 72 minutes!) and tested via a bfu from sxce 101. As soon as I can get past some problems uploading to cr.opensolaris.org[3], I'll get a webrev up. 3.http://opensolaris.org/jive/thread.jspa?messageID=304165&tstart=0 -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ dtrace-discuss mailing list [email protected]
