From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Han-Wen Nienhuys Newsgroups: gmane.comp.gnu.lilypond.devel,gmane.lisp.guile.devel Subject: Re: The usage of -dtrace-scheme-coverage in Lilypond Date: Fri, 11 Mar 2011 10:31:20 -0300 Message-ID: References: Reply-To: hanwen@xs4all.nl NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1299850300 7810 80.91.229.12 (11 Mar 2011 13:31:40 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 11 Mar 2011 13:31:40 +0000 (UTC) Cc: guile-devel@gnu.org, lilypond-devel To: zhangxy Original-X-From: lilypond-devel-bounces+gnu-lilypond-devel=m.gmane.org@gnu.org Fri Mar 11 14:31:35 2011 Return-path: Envelope-to: gnu-lilypond-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Py2RL-0002fm-16 for gnu-lilypond-devel@m.gmane.org; Fri, 11 Mar 2011 14:31:35 +0100 Original-Received: from localhost ([127.0.0.1]:47669 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Py2RK-0000RN-9C for gnu-lilypond-devel@m.gmane.org; Fri, 11 Mar 2011 08:31:34 -0500 Original-Received: from [140.186.70.92] (port=44848 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Py2RE-0000RI-6L for lilypond-devel@gnu.org; Fri, 11 Mar 2011 08:31:29 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Py2RA-0004Ba-4h for lilypond-devel@gnu.org; Fri, 11 Mar 2011 08:31:28 -0500 Original-Received: from mail-ww0-f49.google.com ([74.125.82.49]:59174) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Py2R9-0004BV-TV; Fri, 11 Mar 2011 08:31:24 -0500 Original-Received: by wwc33 with SMTP id 33so2656571wwc.30 for ; Fri, 11 Mar 2011 05:31:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=zQ87I4FKJqNxiU2tYKbq2g+kunGZ7D5+g/WlFJ7c6wY=; b=ixnyEcVQi8RmFp4vr1rWTBGS/iA8ZbilW1Ch59nspATlxehQASRAOg8szfhTnKS/VJ ZRQacVpVOj2qbUP5/Y0cuoQzJlcmT0+QOmY8Ip5lgHkO4pst1azB5oL8vHeKkhlQNwNs fIGqonrqxybu2SMaBw45FPyVaLl04zWQ4t5dQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=JM4UdX8NFzI2wZz8s5UxdWngdnu3qeYZNhpK5/DSyzzv5BpOWX8ADNuw197fAQ6g0n LRQAy8QIkiniSW+j1dXgG+YWuoH8OqnIResCatKM1nLh9HJwu/YyQMoAWKVtq0kvsC9m t/ouxoc0FlyFRHDJjGL6NIqsMUzuj0lvUcNpw= Original-Received: by 10.216.62.67 with SMTP id x45mr6029705wec.92.1299850280817; Fri, 11 Mar 2011 05:31:20 -0800 (PST) Original-Received: by 10.216.241.194 with HTTP; Fri, 11 Mar 2011 05:31:20 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 74.125.82.49 X-BeenThere: lilypond-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on LilyPond development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: lilypond-devel-bounces+gnu-lilypond-devel=m.gmane.org@gnu.org Errors-To: lilypond-devel-bounces+gnu-lilypond-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.comp.gnu.lilypond.devel:35097 gmane.lisp.guile.devel:11851 Archived-At: On Fri, Mar 11, 2011 at 12:21 AM, zhangxy wrot= e: > Dear hanwen, > Now I want to analyze the test coverage of Lilypond. I find the option > -dtrace-scheme-coverage. It says that=C2=A0the option=C2=A0can record cov= erage of > Scheme files in `FILE.cov'. Then I do the following >> >> lilypond -dtrace-scheme-coverage test.ly > > But it gives me the error >> >> throw from within critical section. trace-scheme-coverage relies on a hack in the GUILE evaluator that I added in 2007, which records a symbol's source location the moment that symbol is looked up. The glue on the lilypond side is in scm/coverage.scm. This feature was removed in 2010, when the GUILE folks rewrote the evaluator, before ever seeing the light in a GUILE release. Apparently there is a new mechanism for finding coverage. See https://www.gnu.org/software/guile/manual/html_node/Code-Coverage.html - perhaps you can work out a way with the guile folks to resurrect lilypond's test coverage code. --=20 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen