GNU bug report logs - #68895
Difference between trace behavior in guix repl and guile

Previous Next

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

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

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

From: Adriel Dumas--Jondeau <leirda <at> disroot.org>
To: bug-guix <at> gnu.org
Subject: Difference between trace behavior in guix repl and guile
Date: Fri, 02 Feb 2024 17:21:37 +0100

[Message part 1 (text/plain, inline)]

Here's what's happening in a guix repl:

```
(guix-user)> ,use (guix scripts build)
(guix-user)> ,trace (guix-build "hello") ; doesn't output any trace for some reason
```

And here'the same for a guile repl:

```
(guile-user)> ,use (guix scripts build)
(guile-user)> ,trace (guix-build "hello") ; however it does work
trace: |  (guix-build "hello")
trace: |  |  (_ (guix scripts) #:ensure #f)
trace: |  |  (_ #<procedure 7ff4802c5000 at ice-9/boot-9.scm:3241:7 ()>)
trace: |  |  |  (lock-mutex #<mutex 7ff487d01fc0>)
...
```

This was observed during a working group on profiling during the Guix Days.

-- 
Adriel

[signature.asc (application/pgp-signature, inline)]

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

From: 45mg <45mg.writes <at> gmail.com>
To: Adriel Dumas--Jondeau <leirda <at> disroot.org>, 68895 <at> debbugs.gnu.org
Subject: Re: bug#68895: `guix repl` breaks Guile REPL features
Date: Sat, 04 Jan 2025 13:25:18 -0500

Adriel Dumas--Jondeau <leirda <at> disroot.org> writes:

> (guix-user)> ,use (guix scripts build)
> (guix-user)> ,trace (guix-build "hello") ; doesn't output any trace for some reason

It looks like this isn't the only REPL command that doesn't work in
`guix repl`. I haven't done anything close to a full investigation (I am
new to using Guile!), but many other commands simply don't work.

For example, breakpoints are not respected.
`guix repl`:
--8<---------------cut here---------------start------------->8---
scheme@(guix-user)> (define (my-f x) (+ x 1))
scheme@(guix-user)> ,break my-f
Trap 0: Breakpoint at #<procedure my-f (x)>.
scheme@(guix-user)> (my-f 2)
$1 = 3
--8<---------------cut here---------------end--------------->8---
`guile`:
--8<---------------cut here---------------start------------->8---
scheme@(guix-user)> (define (my-f x) (+ x 1))
scheme@(guix-user)> ,break my-f
Trap 0: Breakpoint at #<procedure my-f (x)>.
scheme@(guix-user)> (my-f 2)
$1 = 3
--8<---------------cut here---------------end--------------->8---

Neither are tracepoints.
`guix repl`:
--8<---------------cut here---------------start------------->8---
scheme@(guix-user)> (define (my-f x) (+ x 1))
scheme@(guix-user)> ,tracepoint my-f
Trap 0: Tracepoint at #<procedure my-f (x)>.
scheme@(guix-user)> (my-f 2)
$1 = 3
--8<---------------cut here---------------end--------------->8---
`guile`:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (define (my-f x) (+ x 1))
scheme@(guile-user)> ,tracepoint my-f
Trap 0: Tracepoint at #<procedure my-f (x)>.
scheme@(guile-user)> (my-f 2)
Trap 0: (my-f 2)
Trap 0: 3
$1 = 3
--8<---------------cut here---------------end--------------->8---

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

From: Suhail Singh <suhailsingh247 <at> gmail.com>
To: 45mg <45mg.writes <at> gmail.com>
Cc: Guix-devel mailing list <guix-devel <at> gnu.org>, 68895 <at> debbugs.gnu.org,
 Adriel Dumas--Jondeau <leirda <at> disroot.org>
Subject: Re: bug#68895: `guix repl` breaks Guile REPL features
Date: Wed, 08 Jan 2025 10:21:45 -0500

45mg <45mg.writes <at> gmail.com> writes:

> It looks like this isn't the only REPL command that doesn't work in
> `guix repl`. I haven't done anything close to a full investigation (I am
> new to using Guile!), but many other commands simply don't work.

Thank you for your investigation.  I am cc-ing guix-devel in case they
have insight regarding these.

-- 
Suhail

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

From: Suhail Singh <suhailsingh247 <at> gmail.com>
To: Suhail Singh <suhailsingh247 <at> gmail.com>
Cc: Guix-devel mailing list <guix-devel <at> gnu.org>, 45mg <45mg.writes <at> gmail.com>,
 68895 <at> debbugs.gnu.org, Adriel Dumas--Jondeau <leirda <at> disroot.org>
Subject: Re: bug#68895: Difference between trace behavior in guix repl and
 guile
Date: Wed, 08 Jan 2025 10:25:28 -0500

Suhail Singh <suhailsingh247 <at> gmail.com> writes:

>> It looks like this isn't the only REPL command that doesn't work in
>> `guix repl`. I haven't done anything close to a full investigation (I am
>> new to using Guile!), but many other commands simply don't work.
>
> Thank you for your investigation.  I am cc-ing guix-devel in case they
> have insight regarding these.

Whoops, sent too quickly.  Current (probably inexhaustive) list:

- trace
- tracepoint
- break

-- 
Suhail

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

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Suhail Singh <suhailsingh247 <at> gmail.com>
Cc: Guix-devel mailing list <guix-devel <at> gnu.org>, 45mg <45mg.writes <at> gmail.com>,
 68895 <at> debbugs.gnu.org, Adriel Dumas--Jondeau <leirda <at> disroot.org>
Subject: Re: bug#68895: Difference between trace behavior in guix repl and
 guile
Date: Tue, 21 Jan 2025 23:15:03 +0900

Hello,

Suhail Singh <suhailsingh247 <at> gmail.com> writes:

> Suhail Singh <suhailsingh247 <at> gmail.com> writes:
>
>>> It looks like this isn't the only REPL command that doesn't work in
>>> `guix repl`. I haven't done anything close to a full investigation (I am
>>> new to using Guile!), but many other commands simply don't work.
>>
>> Thank you for your investigation.  I am cc-ing guix-devel in case they
>> have insight regarding these.
>
> Whoops, sent too quickly.  Current (probably inexhaustive) list:
>
> - trace
> - tracepoint
> - break

Perhaps Guix configures Guile to use the no-debug VM even for the REPL?
Se the '--no-debug' documentation in info '(guile) Command-line
Options':

   ‘--debug’
        Start with the debugging virtual machine (VM) engine.  Using the
        debugging VM will enable support for VM hooks, which are needed for
        tracing, breakpoints, and accurate call counts when profiling.  The
        debugging VM is slower than the regular VM, though, by about ten
        percent.  *Note VM Hooks::, for more information.

        By default, the debugging VM engine is only used when entering an
        interactive session.  When executing a script with ‘-s’ or ‘-c’,
        the normal, faster VM is used by default.

Indeed, if you look at the shebang of scripts/guix.in, which is the
template for the 'guix' entry point script, it uses the '-s' argument.

I'm not sure if there's a way to enable the debug VM after Guile was
started in the equivalent of --no-debug.

-- 
Thanks,
Maxim

Previous Next

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