[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debugging help: how to read/use a backtrace?
From: |
Jan Nieuwenhuizen |
Subject: |
Re: debugging help: how to read/use a backtrace? |
Date: |
Tue, 07 Mar 2017 16:42:21 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Andy Wingo writes:
> On Sat 21 Jan 2017 11:21, Jan Nieuwenhuizen <address@hidden> writes:
>
>> I often find myself struggling to pinpoint an error location from
>> Guile's backtrace (see below) and I am starting to wonder if there is
>> something that I'm missing.
>
> I believe this is comprehensively cleaned up and improved in 2.1.x.
> (Guile 2.0 tries to identify the procedure by looking at slot 0; Guile
> 2.2 instead uses the instruction pointer of the frame.) Can you
> confirm?
Sadly no; this is 2.1.x (x=5 probably) as you can see from this bit
l/l=#<procedure 13000a0 at ice-9/eval.scm:342:13 (a b c d)>
which points to
((4) (lambda (env)
(lambda (a b c d)
(body (make-env* env a b c d)))))
which in turn suggests that I am missing something/hitting problems
that most of you do not have?
Greetings,
Jan
--
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | AvatarĀ® http://AvatarAcademy.nl
- Re: debugging help: how to read/use a backtrace?,
Jan Nieuwenhuizen <=