public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jesper.quorning at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/108125] New: Suggestion for improving bug-box / reporting on ICE
Date: Thu, 15 Dec 2022 11:23:06 +0000 [thread overview]
Message-ID: <bug-108125-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108125
Bug ID: 108125
Summary: Suggestion for improving bug-box / reporting on ICE
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
Assignee: unassigned at gcc dot gnu.org
Reporter: jesper.quorning at gmail dot com
CC: dkm at gcc dot gnu.org
Target Milestone: ---
Barry Houser @barryhouser:matrix.org 2022-12-15 10:36 [1];
> It would be a lot easier for both parties if the compiler offered to collect the
> necessary data and logs for submitting the bug. If it can detect a bug, then why
> stop there? This is exactly why Apple's products are so successful. It's small
> seemingly insignificant things they get right that makes all the difference. It's
> paid off handsomely. Just their iPhone division > alone is bigger than Microsoft.
> It's hard to believe Apple was on life support 20 years ago.
it would be nice to have more information available in case of ICE;
Like -
* (Symbolic) Stack traceback
* Source code location
* Data structures
[1]: https://gitter.im/ada-lang/Alire.
next reply other threads:[~2022-12-15 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 11:23 jesper.quorning at gmail dot com [this message]
2022-12-15 11:40 ` [Bug ada/108125] " pinskia at gcc dot gnu.org
2023-05-11 15:47 ` ebotcazou at gcc dot gnu.org
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108125-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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).