From: Stefan Kangas <stefankangas@gmail.com>
To: Pip Cet <pipcet@protonmail.com>, 74747@debbugs.gnu.org
Cc: Gregor Zattler <telegraph@gmx.net>
Subject: bug#74747: 30.0.92; scratch/igc: crashes when executing M-x list-packages
Date: Mon, 9 Dec 2024 15:34:19 -0500 [thread overview]
Message-ID: <CADwFkmn-G9jg3qidy0K5gz_BHFY4Awx1UdNE55rUGL7Y3odxjA@mail.gmail.com> (raw)
In-Reply-To: <87frmwhmkk.fsf@protonmail.com>
Pip Cet via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
>> Emacs from scratch/igc started with -Q
>> crashes when I do M-X list-packages. I
>> produced some gdb output, see below.
>
>> I wondered, if such random bug reports
>> are of interest for scratch/igc at all
>> (if not, please drop this bug report,
>> it's in no way crucial to me) and if it
>> is appropriate to post them to the bug
>> tracker. I think it would be helpful if
>> README-IGC would answer this two
>> questions.
>
> That's an excellent suggestion, I think we'll update it to make clearer
> that bug reports such as this one are appreciated and that they should
> go to the ordinary Emacs bug list.
Please do, and thank you.
prev parent reply other threads:[~2024-12-09 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 15:11 bug#74747: 30.0.92; scratch/igc: crashes when executing M-x list-packages Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 15:37 ` Gerd Möllmann
2024-12-09 16:02 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 16:15 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 17:38 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 17:52 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 20:34 ` Stefan Kangas [this message]
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmn-G9jg3qidy0K5gz_BHFY4Awx1UdNE55rUGL7Y3odxjA@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=74747@debbugs.gnu.org \
--cc=pipcet@protonmail.com \
--cc=telegraph@gmx.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).