From: Vladimir Zhbanov <vzhbanov@gmail.com>
To: guile-user@gnu.org
Subject: display-backtrace
Date: Sun, 17 Feb 2019 12:07:08 +0300 [thread overview]
Message-ID: <20190217090708.et4zwsvcjnis7s5c@newvzh.lokolhoz> (raw)
Hi,
Is there a way to not limit backtrace output with current terminal
width setting? When I compile my project which uses autotools and
srfi-64 testing suite, it fails on `make distcheck' stage so I
cannot use REPL for debugging (well, I don't know if it's possible
in such a case). When looking at backtrace, it shows me lots of
parens and lots of ellipses so I don't see real (long) filenames
and procedure names and can only guess what's happening. I use
Emacs `compile' command to run `make'. Showing backtrace lines
without such limitations would be much more helpful.
TIA
--
Vladimir
next reply other threads:[~2019-02-17 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 9:07 Vladimir Zhbanov [this message]
2019-03-01 11:46 ` display-backtrace Mike Gran
2019-03-02 15:20 ` display-backtrace Catonano
2019-03-02 15:23 ` display-backtrace Catonano
2019-03-02 16:03 ` display-backtrace Mike Gran
2019-03-02 17:36 ` display-backtrace Catonano
2019-03-03 14:31 ` display-backtrace Vladimir Zhbanov
2019-04-21 10:15 ` display-backtrace Vladimir Zhbanov
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=20190217090708.et4zwsvcjnis7s5c@newvzh.lokolhoz \
--to=vzhbanov@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).