GNU bug report logs - #26027
(system vm trace) creates no output

Previous Next

Package: guile;

Reported by: Mike Gran <spk121 <at> yahoo.com>

Date: Wed, 8 Mar 2017 17:03:02 UTC

Severity: normal

To reply to this bug, email your comments to 26027 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guile <at> gnu.org:
bug#26027; Package guile. (Wed, 08 Mar 2017 17:03:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mike Gran <spk121 <at> yahoo.com>:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Wed, 08 Mar 2017 17:03:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mike Gran <spk121 <at> yahoo.com>
To: Bug Guile <bug-guile <at> gnu.org>
Subject: (system vm trace) creates no output
Date: Wed, 8 Mar 2017 17:01:58 +0000 (UTC)
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




Information forwarded to bug-guile <at> gnu.org:
bug#26027; Package guile. (Wed, 19 Apr 2017 15:08:01 GMT) Full text and rfc822 format available.

Message #8 received at 26027 <at> debbugs.gnu.org (full text, mbox):

From: Andy Wingo <wingo <at> igalia.com>
To: Mike Gran <spk121 <at> yahoo.com>
Cc: 26027 <at> debbugs.gnu.org
Subject: Re: bug#26027: (system vm trace) creates no output
Date: Wed, 19 Apr 2017 17:07:31 +0200
On Wed 08 Mar 2017 18:01, Mike Gran <spk121 <at> 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




Information forwarded to bug-guile <at> gnu.org:
bug#26027; Package guile. (Fri, 25 Dec 2020 14:46:02 GMT) Full text and rfc822 format available.

Message #11 received at 26027 <at> debbugs.gnu.org (full text, mbox):

From: Tim Van den Langenbergh <tmt_vdl <at> gmx.com>
To: 26027 <at> debbugs.gnu.org
Subject: Re: bug#26027: (system vm trace) creates no output
Date: Fri, 25 Dec 2020 15:45:52 +0100
[Message part 1 (text/plain, inline)]
The various trace commands create VM traps that you have to install to 
the thread-local trap state. See API Reference/Debugging/Traps/Trap 
States in the  manual.

-Tim Van den Langenbergh
[OpenPGP_0xF50AF328D9D1E635.asc (application/pgp-keys, attachment)]
[OpenPGP_signature (application/pgp-signature, attachment)]

This bug report was last modified 4 years and 170 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.