unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36677@debbugs.gnu.org
Subject: bug#36677: [PATCH] Don't truncate backtraces
Date: Wed, 17 Jul 2019 13:57:41 -0400	[thread overview]
Message-ID: <87ef2ownkf.fsf@netris.org> (raw)
In-Reply-To: <20190715202918.92925-1-rob@vllmrt.net> (Robert Vollmert's message of "Mon, 15 Jul 2019 22:29:19 +0200")

Hi Robert,

Robert Vollmert <rob@vllmrt.net> writes:

> * module/system/repl/debug.scm (print-frame): Print full object if
> width keyword is #f.
> * libguile/backtrace.c (display_backtrace_body): Call print-frames
> with #:width #f.
> ---
>
> This change was prompted by recent discussion on the Guix lists:
>   https://lists.gnu.org/archive/html/guix-devel/2019-07/msg00207.html
> In Guix, the truncation of stack traces frequently obscures
> important information due to the long filenames.

I'm sympathetic to this problem, but simply disabling the truncated
printing during backtraces is not workable.  It is quite often the case
that some of the structures printed in backtraces are *huge*, or even
cyclic.

Have you tried setting the COLUMNS environment variable to a larger
value?  I'd prefer a solution along those lines, where the user can set
an environment variable to ask for less truncation in backtraces.

     Thanks,
       Mark





  reply	other threads:[~2019-07-17 17:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 20:29 bug#36677: [PATCH] Don't truncate backtraces Robert Vollmert
2019-07-17 17:57 ` Mark H Weaver [this message]
2019-07-17 18:11   ` Robert Vollmert
2019-07-21 15:35     ` Robert Vollmert
2019-07-21 22:59   ` David Pirotte
2019-07-22  0:33     ` Mark H Weaver
2019-07-25 16:27       ` David Pirotte

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=87ef2ownkf.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=36677@debbugs.gnu.org \
    --cc=rob@vllmrt.net \
    /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).