Re: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.

Maxime Devos wrote: > > I propose to add a link to the bug report in the comments, for future > reference. Also, there is an interest in returning zero values in such > cases: > (that patch didn't work out, but the sentiment is still

[PATCH] Avoid 'frame-local-ref' errors when printing backtrace.

Workaround for . * module/system/vm/frame.scm (frame-call-representation): Treat a binding as "unspecified" if its slot exceeds 'frame-num-locals'. --- module/system/vm/frame.scm | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/module/s

Re: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.

On 22-09-2022 15:53, Andrew Whatson wrote: - (let ((val (frame-local-ref frame (binding-slot binding) - (binding-representation binding + (let* ((slot (binding-slot binding)) +;; HACK: Avoid out-of-range fro

Re: [PATCH] Improve reporting of exception locations

Maxime Devos wrote: > > Do you have some test cases, to > >(1) avoid breaking things again with future changes >(2) and show that this patch is correct? > > There recent-ish was a bug report about exception handling (on IRC), it > would be a unfortunate if whatever the fix for that turned