From: Andy Wingo <wingo@igalia.com>
To: Mike Gran <spk121@yahoo.com>
Cc: 26027@debbugs.gnu.org
Subject: bug#26027: (system vm trace) creates no output
Date: Wed, 19 Apr 2017 17:07:31 +0200 [thread overview]
Message-ID: <87r30ol9l8.fsf@igalia.com> (raw)
In-Reply-To: <1682009727.1324219.1488992518603@mail.yahoo.com> (Mike Gran's message of "Wed, 8 Mar 2017 17:01:58 +0000 (UTC)")
On Wed 08 Mar 2017 18:01, Mike Gran <spk121@yahoo.com> writes:
> 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)
Weird. From an initial glance I don't know why this isn't working.
Irritating!
Andy
next prev parent reply other threads:[~2017-04-19 15:07 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 ` bug#26027: (system vm trace) creates no output Mike Gran
2017-04-19 15:07 ` Andy Wingo [this message]
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=87r30ol9l8.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=26027@debbugs.gnu.org \
--cc=spk121@yahoo.com \
/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).