From owner-freebsd-ruby@FreeBSD.ORG Sat Nov 8 01:47:45 2014 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D475359D; Sat, 8 Nov 2014 01:47:45 +0000 (UTC) Received: from mail.westryn.net (mail.westryn.net [199.48.135.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B84F5AA2; Sat, 8 Nov 2014 01:47:45 +0000 (UTC) Received: from hayden.westryn.net (225x169.ouraynet.com [204.16.225.169]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.westryn.net (Postfix) with ESMTPSA id 3D45C9432D2; Fri, 7 Nov 2014 18:41:42 -0700 (MST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: FreeBSD Port: ruby21-2.1.3_1,1 From: Carol Deihl Date: Fri, 7 Nov 2014 18:41:40 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <430278F3-C8C5-46CD-8D30-0F9882D127EF@westryn.net> To: ruby@FreeBSD.org X-Mailer: Apple Mail (2.1990.1) Cc: ports@FreeBSD.org X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2014 01:47:45 -0000 Hello, I just installed ruby21-2.1.3_1,1 with the DEBUG option *unset*, and when ruby21 is invoked, it prints out: WARNING: number of probes fixed does not match the number of defined = probes (9 !=3D 50, respectively) WARNING: some probes might not fire or your program might crash I haven't used dtrace yet and don't know much about it, but I discovered that if I re-installed the port with DEBUG turned on = (*set*), then the warning messages aren't printed. I'm guessing that the probes.d file in the ruby source arranges to = install some probes at runtime in some routines that don't get compiled into ruby if DEBUG = is off. Is it appropriate to just tell you about this? Should I file a bug = report someplace else? Thank you for your work on the ruby ports! Regards, Carol -- Carol Deihl - carol@westryn.net Shrier and Deihl, Westryn Internet Services Internet Software Development and Hosting Remote Unix Admin, Security http://www.westryn.net/