unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: 26027@debbugs.gnu.org
Subject: bug#26027: (system vm trace) creates no output
Date: Wed, 8 Mar 2017 17:01:58 +0000 (UTC)	[thread overview]
Message-ID: <1682009727.1324219.1488992518603@mail.yahoo.com> (raw)
In-Reply-To: 1682009727.1324219.1488992518603.ref@mail.yahoo.com

Hi-
I created the following file, which I ran under guile-2.0 and master.
There is no tracing output. What am I misunderstanding?
(use-modules 
(system vm trace)) 

(define (write-hi) 
(write "hi")) 

(define (outer) 
(write-hi)) 

(trace-calls-to-procedure write-hi) 
(trace-calls-in-procedure write-hi) 
(trace-instructions-in-procedure write-hi) 
(outer) 

Thanks,
Mike Gran





       reply	other threads:[~2017-03-08 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1682009727.1324219.1488992518603.ref@mail.yahoo.com>
2017-03-08 17:01 ` Mike Gran [this message]
2017-04-19 15:07   ` bug#26027: (system vm trace) creates no output Andy Wingo
2020-12-25 14:45   ` Tim Van den Langenbergh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1682009727.1324219.1488992518603@mail.yahoo.com \
    --to=spk121@yahoo.com \
    --cc=26027@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).