From: Ken Brown <kbrown@cornell.edu>
To: Pip Cet <pipcet@protonmail.com>
Cc: 74805@debbugs.gnu.org
Subject: bug#74805: 30.0.92; Trying to build scratch/igc on Cygwin
Date: Thu, 12 Dec 2024 13:14:16 -0500 [thread overview]
Message-ID: <798ce759-19b8-4ac8-9f52-9c36d9dcd182@cornell.edu> (raw)
In-Reply-To: <87cyhxkck9.fsf@protonmail.com>
On 12/11/2024 6:47 PM, Pip Cet wrote:
> "Ken Brown" <kbrown@cornell.edu> writes:
>
>> I've made a first attempt to port mps to Cygwin. If anyone else is
>> interested in seeing this or helping, you can find my work at
>>
>> https://github.com/kbrow1i/mps-cygwin
>>
>> This is a fork of the mps git repo with two commits on top.
>>
>> With the current attempt, I can build the scratch/igc branch, but there
>> are many test failures. For example, when I run the process-tests, I
>
> But the Emacs binary "works", to some extent? Is there anything in the
> process-tests.log file which hints at what kind of problem it might be?
>
> Does it work interactively, or crash right away?
>
>> get 19 failures and 8 skipped tests. But on the master branch I get no
>> failures and only 3 skipped.
>
> That sounds like a "minor" GC problem; a word size mismatch or alignment
> problem would probably lead to a hard crash, so it's more likely to be a
> problem in scanning the stack.
>
> I'm a bit confused about the role of prmccyi6.c; it's included in the
> cyi6gc.mk fragment, but it's not included by mps.c directly. How are you
> building MPS?
>
> I see that you have defined (in prmccyi6.c)
>
> Addr MutatorContextSP(MutatorContext context)
> {
> AVERT(MutatorContext, context);
> return (Addr)context->ucontext->uc_mcontext.rsp; /* .sp */
> }
>
> using the MutatorContextStruct from prmcix.h, which uses an ucontext.
> However, you also include prmcw3.c, which uses a different definition of
> MutatorContextStruct. I don't think those two are compatible, so it's
> possible that's the problem, depending on how you build mps.
>
>> This probably means that my current attempt to port mps is no good, and
>> I have to go back to the drawing board. Before I do that, however, I'd
>> like to check and see if test failures on scratch/igc are to be
>> expected. Are people testing other platforms seeing this too?
>
> I see a few test failures on Windows, but nothing as catastrophic as
> what you describe.
>
> Do you have a usable debugger/gdb on your platform? That would
> be one approach to diagnosing crashes (if the problem is indeed that
> Emacs crashes). Another approach would be to run the test suite
> included in MPS.
Thanks for the reply and suggestions. See my response to Ely.
Ken
next prev parent reply other threads:[~2024-12-12 18:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 22:50 bug#74805: 30.0.92; Trying to build scratch/igc on Cygwin Ken Brown
2024-12-11 23:47 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 18:14 ` Ken Brown [this message]
2024-12-11 23:57 ` Andrea Corallo
2024-12-12 6:09 ` Eli Zaretskii
2024-12-12 18:12 ` Ken Brown
2024-12-12 19:25 ` Eli Zaretskii
2024-12-12 11:05 ` Stefan Kangas
2024-12-12 11:30 ` Eli Zaretskii
2024-12-12 12:06 ` Gerd Möllmann
2024-12-12 14:38 ` Eli Zaretskii
2024-12-12 15:01 ` Gerd Möllmann
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=798ce759-19b8-4ac8-9f52-9c36d9dcd182@cornell.edu \
--to=kbrown@cornell.edu \
--cc=74805@debbugs.gnu.org \
--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 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).