From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35542@debbugs.gnu.org, Mathieu Othacehe <m.othacehe@gmail.com>
Subject: bug#35542: Installer does not display full backtrace on error
Date: Sat, 4 May 2019 19:40:32 +0200 [thread overview]
Message-ID: <20190504174032.r756yfjld5gqyabh@pelzflorian.localdomain> (raw)
In-Reply-To: <20190504173807.2fxseiyoa4nvaoae@pelzflorian.localdomain>
On Sat, May 04, 2019 at 07:38:07PM +0200, pelzflorian (Florian Pelz) wrote:
> On Sat, May 04, 2019 at 07:06:17PM +0200, Danny Milosavljevic wrote:
> > So I'd be for either presenting the entire backtrace or suppressing the
> > entire backtrace, not having teaser backtraces :)
>
> Let’s assume someone is getting an error in the installer for some
> reason. If they are Guix developers, maybe they understand the issue
> from the (trimmed) backtrace. If they are not well-versed in Unix,
> with the backtrace they can exfiltrate the (trimmed) error with a
> camera. I hope I understand the purpose correctly. Maybe it saves
> the people on the mailing list complicated explanations. These maybes
> become more likely with a fuller backtrace, I suppose.
>
On the other hand the error message after the backtrace is hopefully
enough most of the time. But maybe it is not.
Regards,
Florian
next prev parent reply other threads:[~2019-05-04 17:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 8:59 bug#35542: Installer does not display full backtrace on error pelzflorian (Florian Pelz)
2019-05-03 9:40 ` Danny Milosavljevic
2019-05-03 10:09 ` Ludovic Courtès
2019-05-03 12:15 ` Mathieu Othacehe
2019-05-03 17:46 ` pelzflorian (Florian Pelz)
2019-05-04 9:43 ` Mathieu Othacehe
2019-05-04 12:24 ` pelzflorian (Florian Pelz)
2019-05-04 12:54 ` Danny Milosavljevic
2019-05-04 16:14 ` Mathieu Othacehe
2019-05-04 16:15 ` Mathieu Othacehe
2019-05-08 14:35 ` Ludovic Courtès
2019-05-14 12:09 ` Mathieu Othacehe
2019-05-14 21:02 ` Ludovic Courtès
2019-05-15 7:30 ` Mathieu Othacehe
2019-05-04 17:06 ` Danny Milosavljevic
2019-05-04 17:38 ` pelzflorian (Florian Pelz)
2019-05-04 17:40 ` pelzflorian (Florian Pelz) [this message]
2019-05-04 17:26 ` pelzflorian (Florian Pelz)
2019-05-14 16:01 ` Danny Milosavljevic
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190504174032.r756yfjld5gqyabh@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=35542@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=m.othacehe@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).