From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: luangruo@yahoo.com, kirill@korins.ky, 71712@debbugs.gnu.org
Subject: bug#71712: 29.3; Crash on OpenBSD
Date: Mon, 01 Jul 2024 19:04:27 +0300 [thread overview]
Message-ID: <86sewtdrp0.fsf@gnu.org> (raw)
In-Reply-To: <87h6d9qgz5.fsf@ledu-giraud.fr> (message from Manuel Giraud on Mon, 01 Jul 2024 17:17:34 +0200)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: kirill@korins.ky, luangruo@yahoo.com, 71712@debbugs.gnu.org
> Date: Mon, 01 Jul 2024 17:17:34 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> [...]
>
> >> +# https://debbugs.gnu.org/cgi/bugreport.cgi?bug=71712#8
> >> +CFLAGS = -O0 -g3
> >> +CONFIGURE_ARGS+= --enable-checking='yes,glyphs' \
> >> + --enable-check-lisp-object-type
> >> +
> >> DEBUG_PACKAGES = ${BUILD_PACKAGES}
> >>
> >> FLAVORS= athena gtk2 gtk3 no_x11
> >>
> >>
> >> and run make upgrade to upgrade this port
> >
> > Thanks. So an unoptimized build doesn't crash. My suggestion would
> > be to try a build with "-O1 -g3" and see if that works for you.
>
> FWIW, it also does not crash on "normal" build of emacs master branch.
Not sure I understand: what was not "normal" in Kirill's build where
he originally saw the crashes?
next prev parent reply other threads:[~2024-07-01 16:04 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
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 [this message]
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=86sewtdrp0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71712@debbugs.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 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).