From: <tomas@tuxteam.de>
To: 40008@debbugs.gnu.org
Subject: bug#40008: Backtraces can contain very long strings
Date: Tue, 10 Mar 2020 12:47:11 +0100 [thread overview]
Message-ID: <20200310114711.GA10381@tuxteam.de> (raw)
In-Reply-To: <CAPsXM8VQHXCREX9At-4i2WjCaJGwuFZaJ2WcopsqN7dK7e_F8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]
On Tue, Mar 10, 2020 at 11:05:24AM +0100, Jan Synacek wrote:
> I have the following backtrace:
>
> Backtrace:
> In ice-9/boot-9.scm:
> 1736:10 9 (with-exception-handler _ _ #:unwind? _ # _)
> In unknown file:
> 8 (apply-smob/0 #<thunk 651b40>)
> In ice-9/boot-9.scm:
> 718:2 7 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
> In ice-9/eval.scm:
> 619:8 6 (_ #(#(#<directory (guile-user) 74cf00>)))
> In ice-9/boot-9.scm:
> 2806:4 5 (save-module-excursion _)
> 4351:12 4 (_)
> In /home/jsynacek/./git.scm:
> 72:0 3 (_)
> 61:16 2 (change-spec _ _ "66.33" _ #<output: file 1>)
> 48:12 1 (change-release "# We ship a .pc file but don't want t…" …)
> In unknown file:
> 0 (make-regexp "^Release:(\\s*).*$" "# We ship a .pc fil…" …)
>
> ERROR: In procedure make-regexp:
> Wrong type (expecting exact integer): "
> <HERE COMES A LOOOONG STRING WHICH IS ABOUT 193000 CHARACTERS WIDE>
> "
>
> While this is probably not considered an error, I guess it might be better
> to ellipsize strings in errors such is mine that are over a certain length
> long. The important part of the backtrace was scrolled away and I got
> confused about the string, as I thought it was part of the output and
> started wondering why (display ...) keeps the escaped newlines in the
> string.
Some want it, some want it not. I remember a couple of discussions
in guile-user and guile-devel about this topic.
Have you tried setting debug options `width' and/or `depth' (cf. procedure
`debug-options')?
(my current defaults are 79 columns/20 rows, this is Guile 3.0).
> If this is not considered a bug, please, at least consider it an RFE.
I guess one could argue about the current defaults, but it'll be
difficult to find values making all people happy all the time.
Cheers
-- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-03-10 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 10:05 bug#40008: Backtraces can contain very long strings Jan Synacek
2020-03-10 11:47 ` tomas [this message]
2020-03-11 11:13 ` Ludovic Courtès
2020-03-11 12:39 ` Mikael Djurfeldt
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=20200310114711.GA10381@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=40008@debbugs.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).