unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kirill A. Korinsky <kirill@korins.ky>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 71712@debbugs.gnu.org
Subject: bug#71712: 29.3; Crash on OpenBSD
Date: Thu, 27 Jun 2024 14:36:09 +0100	[thread overview]
Message-ID: <5e1e90d2882be9dc@mx2.catap.net> (raw)
In-Reply-To: <86wmma4lb2.fsf@gnu.org>

On Thu, 27 Jun 2024 13:33:37 +0100,
Eli Zaretskii <eliz@gnu.org> wrote:
> 
> Too bad.  How do people debug programs on OpenBSD, if GDB doesn't work
> there?
>

Here a tricky part: I have used GDB on OpenBSD more than once, which
includes attaching to a process on my mail servers when I hunt a bugs inside
it. And it works well.

Emacs is the first application which I can't debug on OpenBSD.


> > So, I run it with better core dump as the only option that I have.
> 
> Then I'm not sure we will be able to solve this bug, at least not
> without a lot of printf-debugging and examining the possibly
> voluminous output.

Probably here is third approach.

You had said that this is possible to achive it from elisp. This is
something new, and I use doomemacs as the base for my config. I haven't
touched mine config recently, but doomemacs were upgraded. The good news it
had one large upgrade with few dozen commits since April [1].

Probably I ma use the diff of changes to find potential bad call or
callback.

Footnotes:
[1]  https://github.com/doomemacs/doomemacs/commits/master/?after=a24ff58a5afea0f2ba1bab85cc39f5c49a688e97+34

-- 
wbr, Kirill





  reply	other threads:[~2024-06-27 13:36 UTC|newest]

Thread overview: 34+ 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 [this message]
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
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

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=5e1e90d2882be9dc@mx2.catap.net \
    --to=kirill@korins.ky \
    --cc=71712@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.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/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).