From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Dave Musicant <dmusicant@carleton.edu>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Trying to understand trace limit
Date: Mon, 5 Oct 2020 11:47:39 -0700 [thread overview]
Message-ID: <CA+XASoUE31TSra+LKwitWdDOjZ5bXJXcwWangbByrOXSNi-Fhg@mail.gmail.com> (raw)
In-Reply-To: <a32acd52-b8f4-b0ed-fbcf-60a3a25dc46d@carleton.edu>
It seems like a bug in 2.2.7 (or even 2.x). I can only suggest reporting it
to bug-guile@gnu.org and guile-devel@gnu.org and update to Guile 3.x.
Aleix
On Sat, Oct 3, 2020 at 1:39 PM Dave Musicant <dmusicant@carleton.edu> wrote:
> I'm using Guile 2.2.7, under Ubuntu 20.04.
>
>
> --
> Dave
>
> On 10/3/20 2:15 AM, Aleix Conchillo Flaqué wrote:
>
>
> Hi Dave,
>
> On Mon, Sep 28, 2020 at 10:06 AM Dave Musicant <dmusicant@carleton.edu>
> wrote:
>
>> Hi all,
>>
>> I'm seeing some strange behavior with tracing code, which I'd love some
>> help understanding. I've boiled it down to the following simplified
>> example:
>>
>> (define count
>> (lambda (n)
>> (if (equal? n 1) 1
>> (+ 1 (count (- n 1))))))
>>
>> ,tr (count 92)
>>
>>
>> When I run the above code (in a fresh Guile instance, via redirecting
>> from a file), the trace runs to completion.
>>
>> However, when I run this version of the code from a file, which runs the
>> function twice...
>>
>> (define count
>> (lambda (n)
>> (if (equal? n 1) 1
>> (+ 1 (count (- n 1))))))
>>
>> ,tr (count 10) ; runs to completion
>> ,tr (count 92) ; dies mid-trace
>>
>>
>> ... then the trace dies when it runs the second time, in something that
>> must be some sort of stack overflow, though the error is fairly cryptic:
>>
>> While executing meta-command:
>> In procedure +: Wrong type argument in position 1: #<unspecified>
>>
>> What's happening from a memory perspective where tracing the code the
>> first time affects how much memory is available for the second time? It
>> seems that the first run shouldn't affect the stack limit of the second,
>> but something is going on.
>>
>> Thanks for the help.
>> Dave
>>
>
> I've tried it with Guile 3.0.4 (in macOS) and I didn't get this error.
> What version of Guile and OS are you using?
>
> Aleix
>
>
>
>
>
prev parent reply other threads:[~2020-10-05 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 17:06 Trying to understand trace limit Dave Musicant
2020-10-03 7:15 ` Aleix Conchillo Flaqué
2020-10-03 20:39 ` Dave Musicant via General Guile related discussions
2020-10-05 18:47 ` Aleix Conchillo Flaqué [this message]
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=CA+XASoUE31TSra+LKwitWdDOjZ5bXJXcwWangbByrOXSNi-Fhg@mail.gmail.com \
--to=aconchillo@gmail.com \
--cc=dmusicant@carleton.edu \
--cc=guile-user@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).