all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58104@debbugs.gnu.org
Subject: bug#58104: 29.0.50; Emacs crushers in console probably by M-w
Date: Wed, 28 Sep 2022 12:09:27 +0300	[thread overview]
Message-ID: <YzQPR857n5uhKMLz@protected.localdomain> (raw)
In-Reply-To: <83r0zwi5yf.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2022-09-28 05:33]:
> > Date: Tue, 27 Sep 2022 23:18:24 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: 58104@debbugs.gnu.org
> > 
> > * Eli Zaretskii <eliz@gnu.org> [2022-09-27 09:43]:
> > > Is this a backtrace from the crash, or is this just a backtrace after
> > > attaching GDB to a running Emacs?  It doesn't look to me as a crash.
> > > It looks like Emacs is idle waiting for input.
> > > 
> > > Is the crash reproducible?
> > 
> > That is backtrace after Emacs crashed. Because it is "often"
> > reproducible, that is why I was running Emacs under gdb.
> 
> It doesn't look like a crash, and the information about the fatal
> signal was missing.

Emacs received SIGINT, that was it.

Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/





  reply	other threads:[~2022-09-28  9:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  5:48 bug#58104: 29.0.50; Emacs crushers in console probably by M-w Jean Louis
2022-09-27  6:42 ` Eli Zaretskii
2022-09-27 20:18   ` Jean Louis
2022-09-28  2:32     ` Eli Zaretskii
2022-09-28  9:09       ` Jean Louis [this message]
2022-09-28 11:57         ` Eli Zaretskii
2022-10-01  3:56           ` Jean Louis
2022-10-01  6:27             ` Eli Zaretskii
2022-10-05 18:50               ` Jean Louis
2022-10-05 19:24                 ` Eli Zaretskii
2022-10-05 19:43                   ` Jean Louis

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=YzQPR857n5uhKMLz@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=58104@debbugs.gnu.org \
    --cc=eliz@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.