[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Incomplete backtrace

From: Christopher Howard
Subject: Incomplete backtrace
Date: Sat, 14 Mar 2020 06:19:57 -0800

I think there are others here better qualified to answer your question,
but maybe one helpful thing: have you read the Guile Implementation
section of the Guile Reference Manual? In subsection "A Virtual Machine
for Guile" there is this paragraph:

Note that once a value in a local variable slot is no longer needed,
Guile is free to re-use that slot.  This applies to the slots that were
initially used for the callee and arguments, too.  For this reason,
backtraces in Guile aren’t always able to show all of the arguments: it
could be that the slot corresponding to that argument was re-used by
some other variable.

I do not know if there is a way to disable slot reuse, for debugging
purposes. Anyone...?

Christopher Howard
p: +1 (907) 374-0257
gpg: ADDEAADE5D607C8D (

> Why do I not see the exact place where the problem is? Why are there
> underscores instead? Why do I not even see that the error originated
> in
> test.scm? I can't find any explanation about this in the manual.
> While this code was extracted from a bigger program and it's obvious
> where
> the problem is, it was super hard to figure it out in the original
> program.
> Because the backtrace actually doesn't even point in the right place,
> it's
> quite useless in my opinion.
> Am I doing anything wrong? I use guile 3.0.1.
> Regards,
> -- 
> Jan Synacek
> Software Engineer, Red Hat

reply via email to

[Prev in Thread] Current Thread [Next in Thread]