all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Pip Cet <pipcet@protonmail.com>
Cc: Eval EXEC <execvy@gmail.com>,  Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: [scratch/igc] 985247b6bee crash on Linux, KDE, Wayland
Date: Sat, 07 Sep 2024 15:20:50 +0200	[thread overview]
Message-ID: <m25xr761n1.fsf@pro2.fritz.box> (raw)
In-Reply-To: <87o74zevf9.fsf@protonmail.com> (Pip Cet's message of "Sat, 07 Sep 2024 08:10:21 +0000")

Pip Cet <pipcet@protonmail.com> writes:

> "Eval EXEC" <execvy@gmail.com> writes:
>
>> Hello Pie, how did you compile mps with `-g3 -ggdb -O0`?
>
> I ended up patching gc.gmk to remove "-Werror" to avoid these (harmless)
> compilation warnings:
>
> https://codeberg.org/pipcet/mps/commit/ea0eabca6908dd750dd2575696193f246ee4d309
>
> modified   code/gc.gmk
> @@ -18,7 +18,6 @@ CFLAGSCOMPILER := \
>  -Waggregate-return \
>  -Wall \
>  -Wcast-qual \
> --Werror \
>  -Wextra \
>  -Winline \
>  -Wmissing-prototypes \
>
> A better change is needed, though, to avoid future compiler warnings
> which are appropriate but ought to be non-fatal.
>

I don't know if it has been mentioned before because I didn't read all
of it. Anyway.

In the past, I found configuring --with-mps=debug and
--enable-checking=all,igc_debug,igc_check_fwd helpful, in addition to
what might have been suggested already for CFLAGS, e.g. -g -O0.

That's for Emacs, not MPS.



  reply	other threads:[~2024-09-07 13:20 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05  6:24 [scratch/igc] 985247b6bee crash on Linux, KDE, Wayland Eval EXEC
2024-09-05  7:14 ` Eval EXEC
2024-09-05  8:17   ` Eval EXEC
2024-09-05  7:21 ` Eval EXEC
2024-09-05  8:08 ` Eli Zaretskii
2024-09-05  8:14   ` Eval EXEC
2024-09-05 11:12   ` Pip Cet
2024-09-05  8:24 ` Helmut Eller
2024-09-05  8:28   ` Eval EXEC
2024-09-05  8:34     ` Helmut Eller
2024-09-05  8:37       ` Eval EXEC
2024-09-05 10:44       ` Eval EXEC
2024-09-05 11:01         ` Eli Zaretskii
2024-09-05 11:04           ` Eval EXEC
2024-09-05 11:09 ` Pip Cet
2024-09-05 11:15   ` Eval EXEC
2024-09-05 11:19     ` Pip Cet
2024-09-05 11:26       ` Eval EXEC
2024-09-05 16:04         ` Pip Cet
2024-09-05 16:32           ` Eval EXEC
2024-09-05 11:34       ` Eval EXEC
2024-09-05 11:49       ` Eval EXEC
2024-09-05 12:21         ` Eli Zaretskii
2024-09-05 13:20           ` Gerd Möllmann
2024-09-05 13:31             ` Eli Zaretskii
2024-09-05 13:37               ` Gerd Möllmann
2024-09-05 13:52                 ` Eli Zaretskii
2024-09-05 13:57                   ` Gerd Möllmann
2024-09-05 14:33                     ` Eli Zaretskii
2024-09-05 14:44                       ` Eli Zaretskii
2024-09-05 14:58                       ` Gerd Möllmann
2024-09-05 16:19                       ` Pip Cet
2024-09-05 16:40                         ` Eval EXEC
2024-09-05 16:45                         ` Eval EXEC
2024-09-05 16:57                         ` Eval EXEC
2024-09-05 16:59                           ` Eval EXEC
2024-09-05 17:03                           ` Pip Cet
2024-09-05 17:05                             ` Eval EXEC
2024-09-05 17:16                               ` Gerd Möllmann
2024-09-05 18:46                                 ` Eli Zaretskii
2024-09-05 19:24                                   ` Gerd Möllmann
2024-09-05 19:31                                     ` Eli Zaretskii
2024-09-05 18:48                               ` Eli Zaretskii
2024-09-05 18:56                                 ` Eval EXEC
2024-09-05 19:23                                   ` Eli Zaretskii
2024-09-05 19:31                                     ` Eli Zaretskii
2024-09-06  2:15                                     ` Eval EXEC
2024-09-06  3:10                                       ` Eval EXEC
2024-09-06  5:58                                         ` Pip Cet
2024-09-06  6:32                                           ` Eval EXEC
2024-09-06  7:41                                             ` Pip Cet
2024-09-06  8:28                                               ` Eval EXEC
2024-09-06 12:58                                                 ` Pip Cet
2024-09-06 13:14                                                   ` Eval EXEC
2024-09-06 10:57                                               ` Eli Zaretskii
2024-09-06 13:03                                                 ` Eval EXEC
2024-09-06 19:29                                             ` Pip Cet
2024-09-07  5:57                                               ` Eli Zaretskii
2024-09-07  9:05                                                 ` Pip Cet
2024-09-06  6:39                                           ` Eval EXEC
2024-09-06  7:43                                             ` Pip Cet
2024-09-07  7:46                                               ` Eval EXEC
2024-09-07  8:10                                                 ` Pip Cet
2024-09-07 13:20                                                   ` Gerd Möllmann [this message]
2024-09-06  6:05                                         ` Eli Zaretskii
2024-09-06  6:30                                           ` Pip Cet
2024-09-06  6:34                                           ` Eval EXEC
2024-09-06 11:49                                             ` Eli Zaretskii
2024-09-06 13:08                                               ` Eval EXEC
2024-09-05 19:01                                 ` Eval EXEC
2024-09-05 17:29                             ` Eval EXEC

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=m25xr761n1.fsf@pro2.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=execvy@gmail.com \
    --cc=pipcet@protonmail.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.