From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Panicz Maciej Godek <godek.maciek@gmail.com>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Where is the backtrace?
Date: Fri, 3 Jan 2014 14:57:33 +0100 [thread overview]
Message-ID: <CAMFYt2Yoqn49Ypn75FgU+tKV4hRvyf6GWiKkz4=FzmvBQeUZvQ@mail.gmail.com> (raw)
In-Reply-To: <87d2k9e4va.fsf@Kagami.home>
2014/1/3 Ian Price <ianprice90@googlemail.com>:
[...]
>> Why isn't the information about the subsequent procedures tracked? Do
>> they all get inlined?
>
> scheme@(guile-user)> ,optimize (define (f) (define (g) (define (h) ((lambda x (cdr x)))) (h)) (g))
> $2 = (define (f) (cdr '()))
>
> So, yes.
>
> Though not relevant to this case, there is also another important factor
> in your code, which is that all function calls are tail calls. So even
> if you turned off optimisation, you would not see a complete backtrace.
I've checked this with other implementations. Racket, Gambit and Biwa
Scheme were equally uninformative. Kawa's backtrace was a nightmare to
me, but perhaps someone with more knowledge would be able to infer the
actual location of the error. Actually, the only implementation that
exposed the exact location was Chicken. It proves that there must be a
way to track this information in spite of TCO.
next prev parent reply other threads:[~2014-01-03 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 2:30 Where is the backtrace? Panicz Maciej Godek
2014-01-03 10:28 ` Ian Price
2014-01-03 13:57 ` Panicz Maciej Godek [this message]
2014-01-03 16:15 ` Ian Price
2014-01-03 18:03 ` Mark H Weaver
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='CAMFYt2Yoqn49Ypn75FgU+tKV4hRvyf6GWiKkz4=FzmvBQeUZvQ@mail.gmail.com' \
--to=godek.maciek@gmail.com \
--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).