From: Catonano <catonano@gmail.com>
To: guile-user@gnu.org
Subject: backtraces
Date: Wed, 14 Sep 2016 16:05:19 +0200 [thread overview]
Message-ID: <CAJ98PDwdyDixb2Ai_P13aW86T1X=6OjQOEuAWEjjyLDFK_gb_Q@mail.gmail.com> (raw)
Hello guilers
I am playing a little bit with guile 2.0.11
It happens that one of my functions gets called with an argument of the
wrong type. It should be a hash-table and it's a symbol instead.
So it happens that my function calls hash-fold with something that should
be a hash-table but it's a symbol
Like this:
(hash-fold
first-argument ;; an anonymous function
second-argument ;; this is a long list
'this-should-be-a-hash-table-and-its-not!! )
Thing is that the way the stacktrace gets printed in the debugger is like
this
0 (hash-fold #<procedure 2089e40 at npmjs.scm:72:5 (name version store)>
(#<<npm-package-version> name: "promises-aplus-tests" version: "latest">
#<<npm-pa…>) #)
That is the last argument, the faulty one, is not printed, it's cut out
How can I get my calls completely printed out ?
Because I send different alarm symbols based on the specific error
condition that I get, having those printed out would be neat.
Instead of having to reconstruct in the REPL the whole call chain to see
which error actually arose.
reply other threads:[~2016-09-14 14:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJ98PDwdyDixb2Ai_P13aW86T1X=6OjQOEuAWEjjyLDFK_gb_Q@mail.gmail.com' \
--to=catonano@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).