From: Kirill A. Korinsky <kirill@korins.ky>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: luangruo@yahoo.com, Eli Zaretskii <eliz@gnu.org>, 71712@debbugs.gnu.org
Subject: bug#71712: 29.3; Crash on OpenBSD
Date: Thu, 27 Jun 2024 15:43:20 +0100 [thread overview]
Message-ID: <5e1e913eeab727e7@mx2.catap.net> (raw)
In-Reply-To: <m27ceao4cg.fsf@pro2.fritz.box>
On Thu, 27 Jun 2024 15:19:43 +0100,
Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
>
> Not sure about OpenBSD, but FreeBSD switched to LLVM, i.e. clang and
> lldb, a while ago. Do you have these?
I do, and attemt to use it looks like:
~ $ lldb /usr/local/bin/emacs
(lldb) target create "/usr/local/bin/emacs"
Current executable set to '/usr/local/bin/emacs' (x86_64).
(lldb) r
Process 21865 launched: '/usr/local/bin/emacs' (x86_64)
and nothing had happened. I wait couple of minutes, but after I pres C-c it,
at least exits as:
Process 21865 exited with status = -1 (0xffffffff) lost connection
anyway, it left the process:
~ $ ps aux | grep 21865
catap 21865 0.0 0.3 21200 42672 p2 TX 3:35PM 0:00.29 /usr/local/bin/emacs (emacs-29.4)
catap 71388 0.0 0.0 792 1448 p2 S+p 3:41PM 0:00.00 grep 21865
~ $
what means that debuging emacs doesn't work.
I've tried to debug xterm and it works like a charm via bot lldb and gdb.
--
wbr, Kirill
next prev parent reply other threads:[~2024-06-27 14:43 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
2024-06-27 14:19 ` Gerd Möllmann
2024-06-27 14:43 ` Kirill A. Korinsky [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5e1e913eeab727e7@mx2.catap.net \
--to=kirill@korins.ky \
--cc=71712@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--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 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.