all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 71712@debbugs.gnu.org, kirill@korins.ky
Subject: bug#71712: 29.3; Crash on OpenBSD
Date: Mon, 01 Jul 2024 11:10:50 +0200	[thread overview]
Message-ID: <877ce5scit.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <790c3123fb846ef4@mx2.catap.net> (Kirill A. Korinsky's message of "Sun, 30 Jun 2024 23:58:53 +0100")

Kirill A. Korinsky <kirill@korins.ky> writes:

[...]

> No, because I've used egdb already. Frankly speaking I can't do it via gdb,
> lldb and egdb. It simple goes to a state which locks like a deadlock. I
> can't kill emacs or used debuger, and the only way to ride off that
> processes is reboot.
>
> Futuremore, at least once I achived a kernel panic [1] by my attempt to
> debug emacs. This was confirmed as bug by mpi@ [2] and claudio@ [3] who had
> planned to improve it.
>
> BTW, since I've rebuild emacs as suggested [4] I haven't faced any
> crash.

Thanks for all this backstory.  I've never faced a kernel panic from
emacs myself.
-- 
Manuel Giraud





  reply	other threads:[~2024-07-01  9:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-22  0:01 bug#71712: 29.3; Crash on OpenBSD Kirill A. Korinsky
2024-06-22  1:24 ` Stefan Kangas
2024-06-22  7:45 ` Eli Zaretskii
2024-06-22  9:28   ` Kirill A. Korinsky
2024-06-22 10:00     ` Eli Zaretskii
2024-06-22 11:00       ` Kirill A. Korinsky
2024-06-22 12:59       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-22 14:41         ` Kirill A. Korinsky
2024-06-22 15:55           ` Eli Zaretskii
2024-06-26  9:11             ` Kirill A. Korinsky
2024-06-26 13:14               ` Eli Zaretskii
2024-06-26 15:58                 ` Kirill A. Korinsky
2024-06-26 16:11                   ` Eli Zaretskii
2024-06-26 22:00                     ` Kirill A. Korinsky
2024-06-27  5:33                       ` Eli Zaretskii
2024-06-27 11:44                         ` Kirill A. Korinsky
2024-06-27 12:33                           ` Eli Zaretskii
2024-06-27 13:36                             ` Kirill A. Korinsky
2024-06-27 14:19                               ` Gerd Möllmann
2024-06-27 14:43                                 ` Kirill A. Korinsky
2024-06-27 15:01                                   ` Gerd Möllmann
2024-06-30  8:52                               ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-30 16:42                                 ` Kirill A. Korinsky
2024-06-30 17:40                                   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-30 22:58                                     ` Kirill A. Korinsky
2024-07-01  9:10                                       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-01 11:18                                       ` Eli Zaretskii
2024-07-01 13:29                                         ` Kirill A. Korinsky
2024-07-01 13:43                                           ` Eli Zaretskii
2024-07-01 15:17                                             ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-01 16:04                                               ` Eli Zaretskii
2024-07-01 16:42                                                 ` Kirill A. Korinsky
2024-07-01 17:36                                                   ` Eli Zaretskii
2024-07-01 18:38                                                     ` Kirill A. Korinsky
2024-08-20 19:13                                             ` Kirill A. Korinsky
2024-08-21 13:23                                               ` Eli Zaretskii

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=877ce5scit.fsf@ledu-giraud.fr \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71712@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kirill@korins.ky \
    --cc=luangruo@yahoo.com \
    --cc=manuel@ledu-giraud.fr \
    /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.